On 23/05/2011 13:35, Daniel Holth wrote:
It is perfectly alright to have 0, 1, or more than one declarative base
class (you will have 0 if you are using the ORM without the declarative
extension). The only limitation I've found is that you have to use class
attributes, not string table names, to reference foreign keys. e.g.
ForeignKey(User.foobar) instead of ForeignKey('usertable.foobar_id')
Right, but if you use mortar_rdb's declarative_base, then you can still
use string keys, which rely on the declarative base's class registry...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
