4 ms·

Hum yeah, it shows. Just the fact that the API looks completely different for Postgre and SQLite tells us everything we need to know about the quality of the pr

Hum yeah, it shows. Just the fact that the API looks completely different for Postgre and SQLite tells us everything we need to know about the quality of the project here.

jeswin 1y ago
> Just the fact that the API looks completely different for Postgre and SQLite tells us everything we need to know about the quality of the project here. How does the API look completely different for pg and sqlite? Can you share an example? It's an implementation of LINQ's IQueryable. With some bells missing in DotNet's Queryable, like Window functions (RANK queries etc) which I find quite useful. Add: What you've mentioned is largely incorrect. But in any case, it is a query builder. Meaning, an ORM like database abstraction is not the goal. This allows us to support pg's extensions, which aren't applicable to other database.
pprotas 1y ago
I guess the interesting question is whether @jeswin could have created this project at all if AI tools were not involved. And if yes, would the quality even be better?
- jeswin 1y ago
  Very true. However, to claim that the "API looks completely different for Postgre and SQLite" is disingenuous. What was he looking at?
  - tom_ 1y ago
    There are two examples on the landing page, and they both look quite different. Surely if the API is the same for both, there'd be just one example that covers both cases, or two examples would be deliberately made as identical as possible? (Like, just a different new somewhere, or different import directive at the top, and everything else exactly the same?) I think that's the point. Perhaps experienced users of relevant technologies will just be able to automatically figure this stuff out, but this is a general discussion - people not terribly familiar with any of them, but curious about what a big pile of AI code might actually look like, could get the wrong impression.
    - jeswin 1y ago
      If you're mentioning the first two examples, they're doing different things. The pg example does an orderby, and the sqlite example does a join. You'll be able to switch the client (ie, better-sqlite and pg-promise) in either statement, and the same query would work on the other database. Maybe I should use the same example repeated for clarity. Let me do that. Edit: Fixed. Thank you.
- iLoveOncall 1y ago
  Actually the interesting question is whether this library not existing would have been a loss for humanity. I'll posit that it would not.

Hum yeah, it shows. Just the fact that the API looks completely different for Postgre and SQLite tells us everything we need to know about the quality of the project here.

jeswin 1y ago

> Just the fact that the API looks completely different for Postgre and SQLite tells us everything we need to know about the quality of the project here. How does the API look completely different for pg and sqlite? Can you share an example? It's an implementation of LINQ's IQueryable. With some bells missing in DotNet's Queryable, like Window functions (RANK queries etc) which I find quite useful. Add: What you've mentioned is largely incorrect. But in any case, it is a query builder. Meaning, an ORM like database abstraction is not the goal. This allows us to support pg's extensions, which aren't applicable to other database.

pprotas 1y ago

I guess the interesting question is whether @jeswin could have created this project at all if AI tools were not involved. And if yes, would the quality even be better?

jeswin 1y ago
Very true. However, to claim that the "API looks completely different for Postgre and SQLite" is disingenuous. What was he looking at?
- tom_ 1y ago
  There are two examples on the landing page, and they both look quite different. Surely if the API is the same for both, there'd be just one example that covers both cases, or two examples would be deliberately made as identical as possible? (Like, just a different new somewhere, or different import directive at the top, and everything else exactly the same?) I think that's the point. Perhaps experienced users of relevant technologies will just be able to automatically figure this stuff out, but this is a general discussion - people not terribly familiar with any of them, but curious about what a big pile of AI code might actually look like, could get the wrong impression.
  - jeswin 1y ago
    If you're mentioning the first two examples, they're doing different things. The pg example does an orderby, and the sqlite example does a join. You'll be able to switch the client (ie, better-sqlite and pg-promise) in either statement, and the same query would work on the other database. Maybe I should use the same example repeated for clarity. Let me do that. Edit: Fixed. Thank you.
iLoveOncall 1y ago
Actually the interesting question is whether this library not existing would have been a loss for humanity. I'll posit that it would not.