[twisti]there isnt a UI i can walk by without wishing for free where/order by input
LaSombraI'd kill for any website that shows a list of things to have a DSL for querying
* MikeBux joined #java
* Ragnor joined #java
* yamada joined #java
* acidjnk joined #java
* sepult joined #java
* leppard joined #java
* leppard|2 joined #java
* agnivn joined #java
* agnivn joined #java
dreamreali wonder what that would look like
Para0:0:0:0 TCP/5434
Para5432 even
dreamrealpffft, I'm serious
ParaAll tabular views should init themselves from list of objects -> autoinject per-column filters and sorts.
dreamrealThat's one optio. But would humans use it?
dreamrealLike, actual humans?
dreamrealMaybe it doesn't even matter, hmm, maybe I'm thinking of the problem the wrong way
ParaSolution looking for a problem.
ParaThat would work if one could somehow indicate such lists on page.
ParaAnd then pattern apply the filter selector thingy on it.
dreamrealWell, the website's raison d'etre has to come into play somewhere
* Successus joined #java
deebojust solve paging with offset and fetch n rows only
deebodoes 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
ParaIt's a query strategy.
ParaYou need to support temporal queries for stability, apply sorts, do offsets.
dreamrealdeebo: you kinda need state as part of the process right now
dreamrealso you can treat a website as a db-ish thing, semweb tried it, sort of
dreamrealhave any of you used semweb?
dreamreal(the question is its own answer)
deeboi meant mostly to avoid overhead from offset scrolling to nth page
dreamrealoffset scrolling isn't expensive in a decent db
dreamrealdunno about sqlite, but pretty much every other db is fine
ParaSELECT * 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.
ParaAnother strategy is to cut queried results based on last id from previous page set and then taking next n results based on page size.
dreamrealThe good news about that approach is that you've limited your users to the four who understand SQL *and* your site's data model.
ParaGood, no wasted resources on idiots,.
dreamrealand 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
deeboif you can get index coverage for any combination of filters to avoid table scans it's fine
deebogimme lucene/(open|elastic)search "tables" in my postgres
dreamrealgood news, you already have them :D
dreamrealif you're using postgres you really don't need lucene except for the query language, if that's useful to you
deeboi tested some text search thing with one "backoffice" solution, but a covering index ended up being better and easier to reason about
dreamrealsure
dreamreallucene, 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
* agnivn joined #java
* x1bncwn joined #java
* gustik joined #java
* GreenResponse joined #java
* Successus joined #java
* jamezp joined #java
* computerscience joined #java
computerscienceshould I use java or node
julemand101computerscience: For what problem?
computersciencegetting a graduate developer job in sydney
julemand101I mean, would it not be better you do a research into opening job offerings in your area to see what they look for?
ParaOr if you're interested in some specific field, one might be generally favored over another.
ParaOr if your interests match better with specific ecosystem.
* szkl joined #java
dreamrealcomputerscience: depends on for what, but honestly: node
computersciencewhich node framework
dreamrealnextjs
computerscienceI thought express was better
computersciencemy university taught us express
computersciencemaybe because it's basic
dreamrealdude, 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.
dreamrealnode 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?"
dreamrealThe question itself is a category error.
dreamrealYou wouldn't want an f1 car if you're carrying a load of cordwood. You wouldn't use an F150 on an f1 track.
dreamrealif 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.
* kcomhnall joined #java
* mixfix41 joined #java
* stewi joined #java
* TomyWork joined #java
* sepult joined #java
* stfstfm_ joined #java
* raj joined #java
* MikeBux joined #java
* stfstfm joined #java
* ferdna joined #java
* MikeBux joined #java
* stfstfm_ joined #java
* stfstfm joined #java
* stfstfm__2378 joined #java
* mitch0 joined #java
* stfstfm joined #java
* stfstfm_ joined #java
* P1RATEZ joined #java
* pr070cal joined #java
* stfstfm joined #java
* stfstfm_ joined #java
* sa02irc joined #java
* rvalue- joined #java
* emaczen joined #java
* x1bncwn joined #java
* agnivn joined #java
* geenvoud joined #java
* jamezp joined #java
* pr070cal joined #java
* mindCrime joined #java
* IceMicha| joined #java
* Cyp joined #java
* agnivn joined #java
NeXeNwhy does bytebuddy throw errors and still build properly ?
NeXeNi mean, i see stack traces, but it's just a debug thing in hibernate, but wtf, like i always wondered about that