Back to the channels

#java

05:59 [twisti] databases ruin you for the world
06:00 [twisti] there isnt a UI i can walk by without wishing for free where/order by input
07:32 LaSombra I'd kill for any website that shows a list of things to have a DSL for querying
10:38 dreamreal i wonder what that would look like
10:40 Para 0:0:0:0 TCP/5434
10:40 Para 5432 even
10:41 dreamreal pffft, I'm serious
10:42 Para All tabular views should init themselves from list of objects -> autoinject per-column filters and sorts.
10:43 dreamreal That's one optio. But would humans use it?
10:43 dreamreal Like, actual humans?
10:43 dreamreal Maybe it doesn't even matter, hmm, maybe I'm thinking of the problem the wrong way
10:44 Para Solution looking for a problem.
10:45 Para That would work if one could somehow indicate such lists on page.
10:45 Para And then pattern apply the filter selector thingy on it.
10:47 dreamreal Well, the website's raison d'etre has to come into play somewhere
10:59 deebo just solve paging with offset and fetch n rows only
11:00 deebo does any rdbms support some sort of session / cookie for this? or some sort of cursor that can be navigated both ways without holding on to a connection for the duration
11:01 Para It's a query strategy.
11:01 Para You need to support temporal queries for stability, apply sorts, do offsets.
11:01 dreamreal deebo: you kinda need state as part of the process right now
11:02 dreamreal so you can treat a website as a db-ish thing, semweb tried it, sort of
11:02 dreamreal have any of you used semweb?
11:02 dreamreal (the question is its own answer)
11:02 deebo i meant mostly to avoid overhead from offset scrolling to nth page
11:02 dreamreal offset scrolling isn't expensive in a decent db
11:03 dreamreal dunno about sqlite, but pretty much every other db is fine
11:04 Para SELECT * FROM article WHERE valid_from <= $timestamp AND valid_until > $timestamp ORDER BY valid_from DESC, <other clauses> LIMIT 20 OFFSET 40; -- or whatever is your pagination size and offset etc.
11:05 Para Another strategy is to cut queried results based on last id from previous page set and then taking next n results based on page size.
11:06 dreamreal The good news about that approach is that you've limited your users to the four who understand SQL *and* your site's data model.
11:07 Para Good, no wasted resources on idiots,.
11:09 dreamreal and the site better be a passion project for the author forever, because it's not going to get monetized unless it's selling something, which makes the model untenable in the first place :D
11:11 deebo if you can get index coverage for any combination of filters to avoid table scans it's fine
11:12 deebo gimme lucene/(open|elastic)search "tables" in my postgres
11:12 dreamreal good news, you already have them :D
11:13 dreamreal if you're using postgres you really don't need lucene except for the query language, if that's useful to you
11:13 deebo i tested some text search thing with one "backoffice" solution, but a covering index ended up being better and easier to reason about
11:13 dreamreal sure
11:14 dreamreal lucene, solr, ES are all good bridges to scanning for data; if you really wanted to query it deeply you'd use sparql and rdf, but there's a reason people know about sparql and rdf and they don't know sparql and rdf themselves
13:29 computerscience should I use java or node
13:30 julemand101 computerscience: For what problem?
13:30 computerscience getting a graduate developer job in sydney
13:31 julemand101 I mean, would it not be better you do a research into opening job offerings in your area to see what they look for?
13:48 Para Or if you're interested in some specific field, one might be generally favored over another.
13:48 Para Or if your interests match better with specific ecosystem.
14:16 dreamreal computerscience: depends on for what, but honestly: node
14:17 computerscience which node framework
14:17 dreamreal nextjs
14:18 computerscience I thought express was better
14:18 computerscience my university taught us express
14:18 computerscience maybe because it's basic
14:18 dreamreal dude, you're in #java, asking a question like that. I don't care what you use. If node is an option, the mechanics are broken. Use something else, not our stuff.
14:19 dreamreal node and java are not on the same playing field; it's like saying "I have the choice between an f1 and a ford truck. Which one shoudl I use?"
14:19 dreamreal The question itself is a category error.
14:21 dreamreal You wouldn't want an f1 car if you're carrying a load of cordwood. You wouldn't use an F150 on an f1 track.
14:22 dreamreal if the f150 is an option, then gosh, make the choice and live with it. Node is easy. Asking the question makes it sound like that's a viable metric to use for you. (Java's easy, too, but in completely different ways.) Use what works for you.
22:57 NeXeN why does bytebuddy throw errors and still build properly ?
22:57 NeXeN i mean, i see stack traces, but it's just a debug thing in hibernate, but wtf, like i always wondered about that
23:07 NeXeN it offends my sense of ocd
23:23 jreicher That is curious. What's the error?