Hello! I hope this message may help. I'm an ex-SQLObject user and now
SQLAlchemy user. I just read on the SO group that sqlobject 0.x is being
dropped and a probably backwards incompatible SQLObject 2 is being
developed.
I think SQLAlchemy is more complex but more coherent, and the recent
ActiveMapper function allows any easy, more SQLObject-like database schema
definition, and in fact I think it was created after SO behaviour.
Now, my 2c: do we really need *two* ORMs in the Python community? I think
it's not easy to create an ORM, and dividing two skilled programmers into
two different projects will probably mean that development will be slower.
Multiple unfinished project on the same subject and zero stable-and-usable
software in the same category is already a common issue in the open source
community, we should not make it worse.
There're various SO2 features I'd like to see in SA, mostly related with
SQLobject ease-of-use - in SA everything can be done by creating an
appropriate object, but SQLObject often does it 'out of the box' (e.g.
column overrides).
It would be nice to have a kind of SQLObject class to inherit from in
SQLAlchemy, or something similar. Haven't you (Ian and Micheal) ever
considered a merge?
Please note: I don't want to give unwanted advice. I'm not a skilled
programmer, but I just think there're toooo many 'in progress' software
doing the very same thing in the open source world, and that wastes a lot
of programming time, and often it's not the worse software to reach an
'unmantained' state in the end.
Bye!
--
Alan Franzoni <alan.franzoni.xyz@...>
-
Togli .xyz dalla mia email per contattarmi.
Rremove .xyz from my address in order to contact me.
-
GPG Key Fingerprint:
5C77 9DC3 BD5B 3A28 E7BC 921A 0255 42AA FE06 8F3E
|