11–20 of 25 posts
Earlier quoted context omitted.
When it comes to SQL standard support my bet is always on SQLite before MySQL (except for any multi user/role stuff, of course).
The other exception I'd note is type-related stuff, since, while MySQL isn't always in line with the standard there, SQLite has deliberately chosen a different course than teh standard when it comes to types.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
That's the biggest nerd-out I've seen in weeks.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
So you run tests on SQLite and use Postgres in production? Sounds like a disaster waiting to happen, if it hasn't already.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
is postgres as quick as neo4j, in your use case? ive really been into neo4j lately, but im curious if postgres could also be used as a graph database.
I really liked the cypher query language of neo4j, it was super easy to learn and is way simpler to express complex traversals across a graph. Writing a query in postgres to traverse a graph isn't as straightforward, and unless you're doing it often will take a long time to get used to.
Earlier quoted context omitted.
So you run tests on SQLite and use Postgres in production? Sounds like a disaster waiting to happen, if it hasn't already.
You only test on developer workstations before pushing to production? Sounds like a disaster waiting to happen, if it hasn't already.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
So you run tests on SQLite and use Postgres in production? Sounds like a disaster waiting to happen, if it hasn't already.
This is awesome. I've used WITH RECURSIVE in postgres to do graph traversals (even replaced neo4j with postgres), and now this is also available with sqlite. I can see running tests in development becoming a whole lot easier.
So you run tests on SQLite and use Postgres in production? Sounds like a disaster waiting to happen, if it hasn't already.
Being able to do a "git clone foo; cd foo; do my job" is a great way to start working, especially if you have struggled with front-end stylists using real data and back-end services, or any other specialised, possibly short-term, experts who are working on your project and don't have a need to learn basic db admin skills.
Never mind if you use RAC in production - you're going to make some concessions in your dev environment.