From: Todd Benson <caduceass@...>
Date: 2008-05-26T02:37:29+09:00
Subject: Re: Yup, it's call SQLite! :-)) Re: Is there a One True Postgresinterface? Is Ruby-postgresmaintained?

On Sun, May 25, 2008 at 8:29 AM, Will Parsons <oudeis@nodomain.invalid> wrote:
> Todd Benson wrote:
>> On Thu, May 22, 2008 at 10:40 PM, John Carter <john.carter@tait.co.nz> wrote:
>>> Having started this huge thread on PostgresSQL, I found...
>>>
>>> ....after much swearing at the complexities of setting up users and
>>> passwords and permissions in PostgresSQL.... (I don't care, there will
>>> only ever be one user, why am I battling this stuff?! Bugger this for
>>> a bowl of cherries!)
>>>
>>> ..and now am yet another happy SQLite user.
>>>
>>> Soo so so much simpler.
>>
>> If the shoe fits.  I would use SQLite more if it had proper relational
>> algebra under its hood.
>
> Would you mind explaining what you mean my that?

No solid constraints for data integrity.  Like foreign key
constraints, for example.  Somebody mentioned on this list in a
different thread, though, that this will change in the future.  Here's
a contrived example without caps...

sqlite3 --version
=> 3.4.0
sqlite3

create table food (
  ingredient varchar not null primary key
);

create table measurements (
  measurement varchar not null primary key
);

create table preparation (
  measurement not null references measurements (measurement),
  ingredient not null references food (ingredient),
  primary key (measurement, ingredient)
);

insert into food values ("garlic");
insert into measurements ("clove");
insert into preparation (measurement, ingredient) values ("garlic", "clove");
insert into preparation (measurement, ingredient) values ("clove", "garlic");
select * from preparation;

=> garlic |clove (yes, the result has that space after garlic)
=> clove|garlic

Sort of a bandaid on logic, especially considering that the above code
complies with the SQL92 standard.  Hey, but it's small, fast, and
works for some things.

Sorry for the bad vibe, but people need to be aware that they are not
working with an RDBMS.

Todd