A Minimalist Guide to SQLite • Hacker News Board

Re: A Minimalist Guide to SQLite

#121

Post by justinclift » Fri, Nov 03, 2017, 7:13 PM UTC

Something1234 wrote: post #36

danso wrote: post #29

Very nice! I'm in the middle of writing a book based on SQLite (the overall topic is data analysis with SQL, but SQLite is the medium) while I'm teaching it to students. I used to teach MySQL but it was just so goddamned hard to get it configured correctly on people's computers (I always hated when work had to be done on pre-configured computers lab rather than my own laptop), nevermind the server/client/daemon aspec…

Have you tried sqlitebrowser? It's fantastic, I use it a lot. http://sqlitebrowser.org

Thank you. :)

(I'm one of the dev's on that project)

Re: A Minimalist Guide to SQLite

#122

Post by hexene » Tue, Nov 07, 2017, 4:54 AM UTC

throw2016 wrote: post #85

hexene wrote: post #43

Earlier quoted context omitted.

I'm of course not suggesting you switch back to MySQL, but distributing preconfigured MySQL docker images perhaps might've helped with your configuration troubles.

This kind of use docker comment is being left on most threads to do with setup issues. So you are advocating people who have issues with simple apt-get or yum install mysql or to instead install docker and deal with the complexity of docker, before they can use the app?

It really depends on the use-case, though I'll concede that docker would've been overkill for the parent based on their comment below.

Re: A Minimalist Guide to SQLite

#123

Post by shoeb_uddin » Tue, Nov 07, 2017, 5:30 PM UTC

krallin wrote: post #65

I love SQLite (and use it in a large number of places in our application stack!), but I feel that it suffers from a case of bad defaults. To name a few: - Foreign key checking (and cascading deletion for that matter) are turned off by default. You need to enable them using `PRAGMA foreign_keys = ON;`. - There are practically no downsides (and a number of upsides) to using the WAL journalling mode (at least for "use a…

nice http://ictset.com/skin-care/

Re: A Minimalist Guide to SQLite

#124

Post by shoeb_uddin » Tue, Nov 07, 2017, 5:30 PM UTC

krallin wrote: post #65

I love SQLite (and use it in a large number of places in our application stack!), but I feel that it suffers from a case of bad defaults. To name a few: - Foreign key checking (and cascading deletion for that matter) are turned off by default. You need to enable them using `PRAGMA foreign_keys = ON;`. - There are practically no downsides (and a number of upsides) to using the WAL journalling mode (at least for "use a…

http://ictset.com/skin-care/

Re: A Minimalist Guide to SQLite

#125

Post by ComputerGuru » Fri, Nov 10, 2017, 2:41 AM UTC

bschwindHN wrote: post #88

ComputerGuru wrote: post #80

Earlier quoted context omitted.

How many people run webwpps with changing version requirements for their _database_? Docker is useful for running components of your own code or for isolation, not for managing versions of core applications like a database or a mail server for most people deploying ready-made apps.

Different web apps may use differing DB versions, it happens. I'm merely suggesting docker compose is a fairly simple way to handle this without managing global installations on a dev machine. Keep in mind this is for local development only, I wouldn't use a docker hosted DB in production though you certainly could if you wanted to. I've tried several different dev environment setups and this approach yields the fewe…

I'm not trying to beat a dead horse here, but what kind of app runs on a database version 5 but not version 6 (for example)?

I can see an app relying on features not available in older releases, but databases - of all software - have rock-solid backwards compatibility.

Re: A Minimalist Guide to SQLite

#126

Post by xellisx » Fri, Nov 10, 2017, 7:19 PM UTC

h1d wrote: post #42

xellisx wrote: post #27

Earlier quoted context omitted.

Of course you have sites built with bloated software, like Wordpress...

Only if it were just bloated... Global variables to this day.

That too, and no code/"view" separation.

Re: A Minimalist Guide to SQLite

#127

Post by bschwindHN » Sun, Nov 12, 2017, 9:34 AM UTC

ComputerGuru wrote: post #125

bschwindHN wrote: post #88

Earlier quoted context omitted.

Different web apps may use differing DB versions, it happens. I'm merely suggesting docker compose is a fairly simple way to handle this without managing global installations on a dev machine. Keep in mind this is for local development only, I wouldn't use a docker hosted DB in production though you certainly could if you wanted to. I've tried several different dev environment setups and this approach yields the fewe…

I'm not trying to beat a dead horse here, but what kind of app runs on a database version 5 but not version 6 (for example)? I can see an app relying on features not available in older releases, but databases - of all software - have rock-solid backwards compatibility.

I mean yeah, changing DB minor versions probably won't affect anything, perhaps even changing major versions is alright in most cases.

To me, the value is in reducing the number of potential issues a developer can have in their environment and making the build and runtime as consistent as possible. And when the solution is so easy to use, I don't see much of a downside to the docker approach.

My team switched from Vagrant to docker compose for our development environments and since then we've had much more stability and have wasted much less time tending to them.