Re: [Vala] sqlheavy?

[Evan Nemerson <evan coeus-group com>]

On Thu, 2012-06-21 at 19:56 +0100, ant wrote:
> SQLHeavy is an awesome interface......unfortunately I had to abandon
> it in my project
> because there is (or was) a memory leak  in SQLHeavy.Query. If you
> create one, and
> let it go out of scope, not all the memory is recovered. Search the
> archive for an example.

I don't remember seeing that, and I don't see anything in the
archives...  If you can find a link (or supply a test case) I'd really
like to take a look.

> Having said that, I was creating tens of thousands of the buggers,
> which rapidly became
> an issue on a 4GB VM. If your requirements are less taxing, SQLHeavy
> is well worth
> the price of a few K leakage.
>
> I ended up swiping all the ideas and writing my own wrapper that did
> just enough for
> what I needed....sorry Evan, I'm too thick to fix it properly ;)

If I needed lots of raw performance I'd probably just use sqlite
directly, too.  Actually, I'd probably use something else (leveldb,
tokyo cabinet, etc.) if I could.

> cheers
>
> ant
>
>
> On 21 June 2012 19:24, Evan Nemerson <evan coeus-group com> wrote:
> > On Thu, 2012-06-21 at 10:00 -0400, Brian Duffy wrote:
> > > Hi everyone,
> > >
> > > I need to use sqlite in my app. Does anyone have any experience using the
> > > sqlheavy wrapper? Does it make working with sqlite in Vala more friendly in
> > > your experience? Is it kept up to date?
> >
> > Discalaimer: I wrote SQLHeavy so I can hardly be considered unbiased,
> > but I'll try to be.
> >
> > I've used SQLHeavy quite a bit in some proprietary software (which is
> > why I wrote it), and in my experience it really does make SQLite a lot
> > easier to use.
> >
> > As for keeping it up to date, it's not like SQLite is changing heavily
> > with each release... it's really quite stable, and SQLHeavy doesn't
> > actually need to change.
> >
> > There are a few problems:
> >
> >      * Asynchronous queries can be problematic, especially when not
> >        serialized.  I'm working on rewriting some of the internals to
> >        use Bump [1] to fix that by transparently creating multiple
> >        connections to the database, but my spare time is a bit limited
> >        these days so it is going slowly.
> >      * The ORM generator tool (sqlheavy-gen-orm) is basically crap.
> >        I'm planning on removing it.  I do plan to keep the ORM code in
> >        the library(SQLHeavy.Table, Row, etc.), just don't rely on the
> >        sqlheavy-gen-orm command-line tool.
> >      * libsqlheavy-gtk isn't ready for production use yet.
> >
> >
> > [1] http://code.google.com/p/bump
> >
> > _______________________________________________
> > vala-list mailing list
> > vala-list gnome org
> > https://mail.gnome.org/mailman/listinfo/vala-list
> _______________________________________________
> vala-list mailing list
> vala-list gnome org
> https://mail.gnome.org/mailman/listinfo/vala-list