[Z3-sqlos] next steps for SQLOS

Brian Sutherland jinty at web.de
Tue Apr 18 18:51:02 CEST 2006


Some planned features we discussed on IRC:

Firstly, there seems to be a use case for a public method to sync all
dirty sqlobjects. This would be useful in two cases I see:

    * You are using some traditional SQL and want your changes to
      SQLObjects to be reflected in the database.
    * You want .count() to work reflect recent changes but still want
      to use lazyUpdate. (I see this as a failing in SQLObject, but
      anyway)

This method would be implemented as .syncAllDirty() in a module.


Secondly, these days there is sqlobject2 on the horizon and a zalchemy
project which uses code very similar to that in sqlos. Eventually having
all these in one place would bring advantages in code re-use and
bringing the users of zope+relational object mappers into one place.

As the first baby step in this direction I propose to slowly start
moving sqlobject specific code into a sqlos.zsqlobject by:

    * moving sqlos._sqlos to sqlos.zsqlobject
    * re-document "from sqlos import SQLOS" to
      "from sqlos.zsqlobject import SQLOS"

Comments?

-- 
Brian Sutherland

Metropolis - "it's the first movie with a robot. And she's a woman.
              And she's EVIL!!"



More information about the z3-sqlos mailing list