here the changes i needed to get dbcook (abstraction layer over SA), and its tests going to some extent (70% - relations and expressions are broken): - BoundMetaData -> MetaData - lots (15) - metadata.engine.echo=True - lots (14) Whats the difference between create_engine's echo=boolean and MetaData's echo=boolean ?? - import sqlalchemy.orm - i need mostly 4 things off that, but on lots of places (35): create_session, mapper, relation, clear_mappers. several more things like polymorphic_union, class_mapper etc on single occasions (2-3) *** above 3 are very common - but easy - about each SA-using file - query.get_by_whatever - geee, i didnt know i use it (3) - binaryExpression.operator - operator.xx-builtin and not text (1)
- type_ vs type - too bad, now i need a key-faking dict. (3+2) why, u're afraid type() will become reserved word or what? - mapper.polymorphic_identity without polymorphic_on - i have these, assuming that having no polymorphic_on ignores anything about polymorphism anyway... now it becomes very tricky as for D(C(B(A))) when making D, it does not really know if was A polymorphic or not... it has to get base_mapper and check its polymorphic_on... (3) - Select (and i guess Clause) lost its accept_visitor - sql.compile traversing takes about more recursion levels than before - not really a problem - InstrumentedList gone = my append(key=value) hack gone.. must find the new way (1) - expression translator - simply forget, it relies on way to many internal hooks, and should be rethinked as of new Query and stuff. The hack4repeateability stopped working :-) which was expected. Same about the 'nicer echo of select' hack. ticket/497 - u forgot me.. So: the bulk of changes, line-count-wise is cosmetical; but anything depending on internal hooks/hacks is ... near-dead. i'm not sure if to go 0.4 or stay 0.3, or try being backward compatible. or add a branch. i did backward compatibility before, but now there are way too many changes now. ciao svil >On Friday 27 July 2007 07:36:50 Michael Bayer wrote: > Note that this version has some backwards incompatibilities with 0.3 > > When we get an idea as to how easily people are upgrading to 0.4, > we'll figure out how aggressively we want to patch bug fixes from > 0.4 back into 0.3 and continue releasing on that series. Currently > we plan to keep 0.3 going as long as people need it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
