Kevin Dangoor wrote:
> > * SQLObject schema interpreter: Reads pre-existing tables and generates
> > SQLObject classes based on their contents. Probably not possible to
> > make it 100% accurate, but it would be a nice headstart.
>
> Actually, SQLObject already has the fromDatabase option, which is
> essentially th

I think this one would be pretty cool too, except I think what he's
talking about here is that *actual* code will be generated and put into
a .py file or to stdout. That way, it would be easy to incorporate
existing table designs into sqlobject and then tweak them by hand.
Also, although I haven't tried, I doubt it's smart enough to traverse
foreign keys and realize there are many-to-many or one-to-many
relationships.

The migration idea sounds really good too, I can't think of how many
times I had to add one or more columns.. haven't seen a better way then
doing a manual ALTER TABLE.

By the way, when you guys say "you wouldn't want me mentoring you," are
you just trying to do reverse psychology?

While on the topic of sqlobject, I wouldn't mind seeing a solution that
literally compiled python code into pl/python (for those dbs that
support it) or SQL queries, so that
[i for i in Model.select() if i.name = "Joe"] would translate to SELECT
* from model WHERE name = "Joe" instead of doing the whole select query
and filtering name out in python.

More data types would be useful too, Array comes to mind (its been ansi
for a while), perhaps other ones such as IP..

It could move towards having more ansi support in general, schemas
wouldn't hurt, perhaps (and they could be "prefixes" in non-schema
supporting dbs)
class MySchema(SQLObjectSchema):
    class MyModel(SQLObject):
        foo = ArrayCol()
        addr = IPCol()

Yeah, there's lots of ways to improve SQLObject :).


Speaking of widgets, it also wouldn't hurt to generate KID-html from a
widget so you can do tweaking by hand. I think that would be very cool,
it takes almost no time to use a widget, but if you want something
custom you have to do it from the ground up -- so why not combine the
two?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to