Databases

I need some sort of simple, ease to use database library that can be utilized by C. I'm using it for a non-ENTERPRISE application, so security and all that jazz aren't big deals.

Real men roll their own libraries.

You are describing NDBM or SQLite.

I'm a fan of SQLite.

BerkeleyDB

It's been said twice already, but it has to be SQLite. No Exceptions

After eating most of the calf I look at myself in the mirror. There is grease all over my face. And then I start to eat at random. I bite her little toe. It still smell of her feet. I stab the knife into her arch and see the red meat deep inside. I thrust my fingers inside and dig out the meat and put it in my mouth. It tastes okay. Then I stab the knife into her armpit. Ever since I saw it under her yellow sleeveless top I wondered how it would taste this good.  The wonderful taste cheers me up and I devour her underarm up to the elbow.

Finally I cut off her private parts. When I touch the pubic hair it has a very bad smell. I bite her clit, but it won't come off, it just stretches.  So I throw it in the frying pan and pop it in my mouth. I chew very carefully and swallow it. It is so sweet.

After I swallow it, I feel her in my body and get hot. I turn the body over and open her buttocks, revealing her anus. I scoop it out with my knife and try to put it in my mouth. It smells too much. I put it in the frying pan and throw it in my mouth. It still smells. I spit it out. I go into the next room. It smell of fat, like I've been frying a chicken.

It's been twenty-four hours now. Some huge flies hover and buzz in the bathroom. I try to chase them away, but they came back. They swarm on her face. They seem to tell me that I've lost her forever. It is no longer her. Where is she? She's gone far away. I've broken her. Like a child who breaks his toy. I try to use an electric knife to cut her body. It doesn't work. It just makes a loud sound. I use a hatchet. I strike several times. It's hard work. I strike her thigh. Her body jumps up. If she could feel, it would have hurt.

Finally the thigh separates from her body. I bite it again, like I would bite a chicken leg. Then I cut off her arms. It is even harder than the thigh. I use the electric knife again. It makes a shrill sound, like the sound of her shrill voice. It works this time. Her hand still wears a ring and a bracelet. When I see her long fingers I am driven by another impulse. I use her hand to masturbate. Her long fingers excite me.

When I'm finished I try to bite her finger. I can't. I'm disappointed. I put her hands into the plastic bag along with her legs. And then I see her face. It is still quiet. She has a small nose and a sweet lower lip. When she was alive I wanted to bite them. Now I can satisfy that desire. It's so easy to bite off her nose. As I chew the cartilage I can hear the noise. I use a knife to cut off more of the cartilage and put it in my mouth. It really doesn't taste very good. I scoop out her lower lip with my knife and put it in my mouth. It has hard skin. I decide to eat it later when I can fry it. So I put it in the refrigerator.

Touhou 12g.

http://lmgtfy.com/?q=simple+database

Use Microsoft Access through OLE Automation.

It is the BEST-OF-BREED ROBUST AND SCALABLE TURKEY ENTERPRISE SOLUTION and will maximize your ROI by reducing maintenance costs and empowering users to easily facilitate their own solutions, all while effortlessly synergizing with your corporate strategy and taking your business to the next level.

HAPPY NEW YEAR MY ANUS

>>1
Tossing in another vote for sqlite3. I've used it quite a bit, and it's great.

use the filesystem

Where I come from TURKEY SOLUTION is called gravy.

Every post that doesn't contain the string `SQLite' is trolling.

>>15
Including that one and this one

>>16
Um... I think you might want to reread >>15 again very carefully.

>>17
That's not a string it's a quasiquoted symbol

>>15
You can't use SQLite with C, silly billy.

>>19
0/10

>>18
funny, strstr matches it happily.

>>20
You know, that simplifies to zero no matter what you divide it by.

>>22
0/0

>>22-23
22 has lost. You have one hour to pick up your things and leave /prog/ forever. The Sussman agreed, don't bother him about it.

+1 for sqlite.

BerkleyDB is possibly more powerful, but for personal projects it's not worth the extra effort.

>>25
BerkleyDB is possibly more powerful
ummm what?

>>26

Yes.

From wikipedia:
BDB can support thousands of simultaneous threads of control or concurrent processes manipulating databases as large as 256 terabytes, on a wide variety of operating systems including most Unix-like and Windows systems, and real-time operating systems.

They're both comparable in speed, but BerkleyDB is more oriented toward serious enterprise-level applications and provided functionality there that SQLite can't match. The trade-off being that it's larger, more complicated and less flexible.

SQLite can only handle one thread writing to a database at a time because of it's coarse, database-wide locking mechanism. If you only have one or two threads writing to the database at a time, it's manageable, since each write only takes a few milli-seconds, but that certainly won't work in an enterprise environment.

>>27
SQLite isn't supposed to be a fully featured DBMS, making those concerns pointless. Do you complain that your fridge can't play DVDs?

>>28
SQLite isn't supposed to be a fully featured DBMS.
Neither is BerkleyDB. Far from it. They are actually remarkably similar in the sense that they are _embedded_ database solutions, which is why they are both rather popular in OSS. BerkleyDB doesn't even have a SQL query syntax, IIRC.

I'm not complaining about SQLite. Over the past 5 years I've used SQLite in roughly 80% of my projects. It's fast, small,  and simple. Couldn't ask for more... unless your project needs something that can handle heavy traffic from multiple sources seamlessly. Then you're fucked.

Do you complain that your fridge can't play DVDs?

Yes. All the time.

>>28
That's actually quite a nice idea for the ladies. They wouldn't even need a bed!

>>29
Use the right tool for the job. Complex access and high performance are not within the design scope of SQLite.

BDB sucks. Try shoving more than a couple hundred megabytes into it and it slows to a pathetic crawl.
I tried using it for a project that needed several billion entries, and the only way I could make it perform even *close* to acceptably was to initialize 100 different databases to be opened concurrently and to split the keys I was storing among all of them by hand.

>>32
wrong tool for the job
even mysquirrel would have done better

>>33
Obviously. I was refuting the nonsense in >>25,27.

>>32

Considering the way the BerkleyDB api is designed, this says a heck of a lot more about your code than it does BDB. The API only provides a "get" function for retrieving records, how you search the database is entirely up to you. But you already knew that, right?

It's particularly laughable when you consider the fact that BDB is used by many email servers, tel-com, commercial switches/routers that all regularly handle terabytes worth of data without so much as a hiccup.

For reference: http://www.oracle.com/database/docs/Berkeley-DB-v-Relational.pdf

>By avoiding context switches and minimizing copies, Berkeley DB gets outstanding performance on commodity hardware. ... Read throughput, reading a single record at a time, was 466,623 records per second. Using a high performance bulk retrieval interface for large sequential scans of the database, the same system was able to read 13,501,800 records per second.

*sigh*

If you don't know what BDB is, or how to use it... then chances are you don't need it. SQLite is amazing, and good for almost everything. BDB is, however, not nonsense and extremely powerful if used correctly.

>>35
When my code consists of using that "get" function to look up a record, and that particular line costs roughly four seconds, it's not my code. Sorry.

>>35
When my code consists of using that "get" function to look up a record, and that particular line costs roughly four seconds, it's not my code. Sorry.

>>35
When my code consists of using that "reply" function to duplicate a post, and that particular line costs roughly twelve minutes, it's not my code. Sorry.

>>36-38

I lol'd in my mouth a little.

>>39
I threw up in my anus a little.

>>40
You must be very flexible.

I'm interested in hearing more of the SQLite or BerkeleyDB!! debate.

>>42
Tokyo Cabinet!

>>40-41

I lol'd in my mouth a little.

I'm looking for a Tokyo Cabinet box, it cant be pinku (that's Japanese for pink) or any girl color. It has to be of 2 or more kotoba (that's Japanese for 2 compartments) and has be be chibi (small) sized. And has to be really kawaii (cute). Also It has to be about 10-20 bux. And you have to post pics of it first (i want to make shure it's kawaii [cute]). And it would be nice if it came with matching chopstick holder (WITH chopsticks). OH! and it CANNOT have any cartoon pictures, or be made out of plastic. It has to be made of ceramic, or something like that. Also it would be nice if it was made in japan. and not in china or corea (Korea) or whatever. I have found a bento box similar to the one im describing in e-bay, but it was 1 kotoba, and i don't want my gohan (rice) to touch my other things (it can get wet and i would not like that, plus 2 compartments looks more kawaii)

>>45
Omae, majide baka-kusaizo. Kaere!

I am a database