On Oct 12, 2007, at 12:46 PM, Gaetan de Menten wrote:
> I don't say that everything should be integrated, just the reflection
> part (if at all useful in SA0.4) and the repr methods of the
> corresponding objects (*_repr in formatter.py) which should IMHO
> replace the current repr methods. Or, to say that differently, I don't
> see the point of having a repr method which doesn't produce a ready to
> use string representation of the object if it's possible to do. That's
> what the __repr__ method is for. And here, it's obviously possible
> since you guys do it.
>
which objects are we talking about for __repr__, you mean our attempt
to do this ?
Table('users', MetaData(Engine(sqlite://)), Column('id', Integer(),
primary_key=True, nullable=False), Column('name', String
(length=30,convert_unicode=False), nullable=False), Column
('password', String(length=15,convert_unicode=False)), schema=None)
I dont see how a constructor-capable __repr__ for Table can be
possible considering it needs to be passed in an external MetaData
object.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
