Sorry, I had checked the docs but not the FAQ. I opened a ticket as well, feel free to close it. I think it should be stated in a more clear in way in the docs, though, since it's an unpredictable behaviour.
But was that behaviour present in 0.1.x? I feel a bit estranged about never noticing that. Anyway, I don't see what's the possible drawback of calling the original __init__ . As long as no explicit construction parametr or keyword is required (which was a requirement back in 0.1.x, I think), it shouldn't create any problem, and should be more adherent to sqlalchemy's philosophy of 'not forcing any kind of programming style'. Thank you anyway! -- Alan Franzoni <[EMAIL PROTECTED]> - Togli .xyz dalla mia email per contattarmi. Remove .xyz from my address in order to contact me. - GPG Key Fingerprint (Key ID = FE068F3E): 5C77 9DC3 BD5B 3A28 E7BC 921A 0255 42AA FE06 8F3E --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
