Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

sqlite

Name: Anonymous 2010-01-09 18:14

So I'm looking over the sqlite documentation and I'm thinking that it might be easier to just roll my own solution with fopen, fprintf, etc. What can I practically gain from using a database solution like sqlite?

Name: Anonymous 2010-01-09 18:19

easier future porting to larger sql database

Name: Anonymous 2010-01-09 18:25

SQL. duh.
also, databases rather than flat files.
ffs

Name: Anonymous 2010-01-09 18:30

>>1
Novice troll needs practice.

Name: Anonymous 2010-01-09 18:49

Well, how else could you store data if not in a database? Your program variables don't persist after you restart the program (or your computer, for that matter).

Name: Anonymous 2010-01-09 18:56

>>5
best practices son, best practices.

Name: Anonymous 2010-01-09 19:16

Databases are for information exchange between more than one client. You only need a database if your program isn't fully contained and used locally. Otherwise, that's what the hard drive is for.

Name: Anonymous 2010-01-09 19:57

Rolling your own sounds easier than using sqlite?

Using sqlite is EASY AS FUCK. So unless the only thing you want to do is store unordered fixed-length structs, you're better off using it.

Name: Anonymous 2010-01-09 20:23

Either sqlite, or use the Win32 INI API functions in COBOL
http://www.screenio.com/gui_screenio/gs_htmlhelp_subweb/advanced/windows-apis_inifiles.htm

Name: Anonymous 2010-01-09 21:06

Troll my anus

Name: ( ≖_≖) 2010-01-09 21:35

>>5

Using fopen and fprintf, idiot.

Name: Anonymous 2010-01-11 9:17

I'd love sqlite if it supported stored procedures.

Name: Anonymous 2010-01-11 9:32

>>12
1) Describe a use case where stored procedures could be useful in a local-only database.
2) Propose a lightweight and fast (close to zero-overhead) implementation of stored procedures.

Name: Anonymous 2010-01-11 9:39

I'd love sqlite if it supported database custerware replication, automatic spatial reporting, in-memory transactional partitioning, XML queue multiprocessing, and sandboxed relational cache.

Name: Anonymous 2010-01-11 9:44

I'd love sqlite if it required 50MB of installs and a bloated-as-fuck daemon.

Name: Anonymous 2010-01-11 9:44

I'd love sqlite if upgrading it to the newest version required a complete dump and reload of all the databases.

Name: Anonymous 2010-01-11 9:47

I'd love sqlite if it lost data randomly unconditionally, as opposed to when explicitly running it on an usafe mode to improve performance.

Name: Anonymous 2010-01-11 9:47

I'd love sqlite if it required a lengthly integrity check when it didn't shutdown properly.

Name: Anonymous 2010-01-11 9:49

I'd love sqlite if it didn't run on my mobile phone.

Name: Anonymous 2010-01-11 9:49

I'd love sqlite if it had a more restrictive license.

Name: Anonymous 2010-01-11 9:50

I'd love sqlite if its build system was bigger than the whole of sqlite is big today.

Name: Anonymous 2010-01-11 9:51

>>14 got told

Name: Anonymous 2010-01-11 21:50

I'd love sqlite if I loved sqlite.

Name: Anonymous 2010-01-12 18:00

>>14
It is open-source therefore you should implement it instead of bitching like an ungrateful twat.

Name: Anonymous 2010-01-13 4:12

>>16
You're in luck.  That's exactly what happened last time I upgraded it, because the new version suddenly deemed my create syntax invalid.

Name: Anonymous 2010-01-13 12:36

>>25
Your create syntax was always invalid. You were already dead.

Name: Anonymous 2010-11-02 22:26

Name: Anonymous 2010-11-26 22:24

Name: Anonymous 2011-02-04 18:28

Name: Anonymous 2011-02-04 18:30


Don't change these.
Name: Email:
Entire Thread Thread List