[SQLObject] Releasing 0.4

[Luke O. <lu...@me...>]

Ian et al -

Following on Mohan's problems with 0.3, and restarting a thread from a few
weeks ago, what do you have in mind before releasing 0.4. Haven't seen any
major CVS updates since I submitted the transaction implementation, and we're
using CVS+MemoryTransaction+MultiRegistry+odds&ends in a couple apps about to
go live here. So at least for my use cases, CVS has not revealed any bugs in
the last week or two. How about an 0.4b after the holiday weekend?

Here's my list of maintained changes against CVS, just for the record (and if
anyone thinks they should go in for a new release...):

* Multiple classRegistry's, via optional class-level "_registry" string.

* Converting _defaultOrder to dbcolumn via column lookup if it's in
python-style. (Select orderBy expects db-style, but it makes more sense to me
to specify in python-style.)

* Use of _defaultOrder in Joins performJoin(), for now a naive python sort.

* Minor changes in new (setting inst._connection if passed in), and joins
(using inst's _connection) that make logical sense, and allow
MemoryTransaction to work.

* SQLObject.copyToConnection()

* aliasing of destroy to destroySelf for backwards compatibility until destroy
is meaningful..

* A few miscellaneous columns. Most important, BooleanCol. (However, BooleanCol
doesn't actually work properly with Postgres, as Postgres refuses to accept
integers for BOOL fields; it's a long story. Need to implement toSQL/toPython
Column functionality to fix this. But that's probably for 0.5 :)

* MemoryTransaction, although I'd understand if this were left out of this
release. :) Related note: I need to write some docs on MemoryTransaction
still.


And that's all I've got.

- Luke