Re: [Grecipe-manager-devel] Translation of defaults_en.py (+ SQL discussion)

[Thomas M. H. <tmh...@gm...>]

On 6/2/05, Michael A. Peters <mp...@ma...> wrote:
> On Wed, 2005-06-01 at 23:59 -0300, Leandro Guimar=E3es Faria Corcete Dutr=
a
> wrote:
> > > >         Shame on me for now knowing for sure, but I guess PostgreSQ=
L has a
> > > > means to install an embedded database, where the user doesn't even =
need
> > > > to know about it unless he wants to.
> > >
> > > If so, it would be a viable backend down the line :)
> >
> >       Have to check it someday... might be worthwhile checking how GNUC=
ash,
> > OpenLDAP 2 and others do it.
>=20
> I'm not an SQL person - but what about SQLite?
>=20
> Several projects I know of use SQLite for an embedded database, and I
> believe there are python bindings that are fairly mature.

There is a SQLite backend already implemented for Gourmet, though it's
been several versions since it actually worked :) I stopped putting
time into it when I realized there weren't any instant performance
gains.

There are other optimizations to be made -- probably most of them will
help regardless of the backend. Anyway, I hope to tackle these at some
point, but since Gourmet is fine for my own personal use, it hasn't
become a priority (I'm still not convinced anyone actually finds
having thousands of recipes useful :).  I believe Leandro was
suggesting that PostrgreSQL had some technical advantages over MySQL
or SQLite, which was why he was hoping there was an embedded version
of it.

Tom