Re: database news

[Duncan McGreggor]

On Dec 15, 2007 11:24 AM, <duncan.m...@gmail.com> wrote:
> Great news!
>
[snip]
>
> Next in the queue:
> I've already started on the database storage code work (nothing
> committed to svn yet, though). I've got some stormy ORM code that uses
> twisted support for making asynchronous calls to the database. For the
> first release of the storage code, I'll be configuring pymon to use
> SQLite. Using PostgreSQL or MySQL will be as easy as setting a
> configuration option (and writing the table create statements in SQL).
>
> More soon!
>
> d

"Soon" as arriveed:

I've added the storm-based storage code to svn now. I've got a few
unit tests for the basic operations the pymon will need to perform,
but those need to be fleshed out for all the other operations that
will be needed (and thus will be born the storage API).

d

[duncan.m...@gmail.com]

On Dec 16, 1:02 am, "Duncan McGreggor" <duncan.mcgreg...@gmail.com>
wrote:

> On Dec 15, 2007 11:24 AM, <duncan.mcgreg...@gmail.com> wrote:
>
> > Great news!
>
> [snip]
>
> > Next in the queue:
> > I've already started on the database storage code work (nothing
> > committed to svn yet, though). I've got some stormy ORM code that uses
> > twisted support for making asynchronous calls to the database. For the
> > first release of the storage code, I'll be configuring pymon to use
> > SQLite. Using PostgreSQL or MySQL will be as easy as setting a
> > configuration option (and writing the table create statements in SQL).
>

> > More soon!l
>
> "Soon" as arriveed:

Wow. That was a hell of a typo. Should have been:

"Soon" has arrived:

> I've added the storm-based storage code to svn now. I've got a few
> unit tests for the basic operations the pymon will need to perform,
> but those need to be fleshed out for all the other operations that
> will be needed (and thus will be born the storage API).

That API is now born :-) (though still infantile). More db unit tests
are in place... pymon has a database layer now!

d