On 10/12/07, Simon Pamies <[EMAIL PROTECTED]> wrote:
>
> On Oct 12, 10:09 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote:
> > I couldn't agree more. I mean: shouldn't the "autoload" part be
> > integrated into SQLAlchemy reflection capability if it can do more
> > than SQLAlchemy 0.4 currently support (or simply removed if it doesn't
> > do more)?
>
> As i mentioned in my last reply I'll try to add support for sqlalchemy
> 0.4 in a 0.5 branch of autocode but will maintain an actively
> supported 0.4.x branch.
>
> I don't know how much of the features of autocode should really go
> into sqlalchemy. Model generation tools should IMHO always stay a
> separate part but I'm open for suggestions. I also hate code
> duplication but I think that especially the formatter part should stay
> outside of sqlalchemy: It has a strong relation to the autogeneration
> of the model and as I've learned from my experience with other ORM
> tools, such a feature is better to handle outside the main engine.

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.

If somebody want a more concice/informal representation of an object,
that's what __str__ is for. Anyway, this is just my opinion.

-- 
Gaƫtan de Menten
http://openhex.org

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to