On 6/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I simply installed SA I think .2 adn TG did not run the next day.  I
tried removing all .pyc.  I also tg-admin sql and deleting the old
database and created a new blank one.  The performance was decent
something like 1000 inserts a second for a name table.  When I took the
code out of my model.py file TG exploded (thats just a coincidence
perhaps though).  Does installing SQLAlchemy break Turbogears?

aparently it does check this line http://trac.turbogears.org/turbogears/browser/tags/0.9a6/turbogears/database.py?rev=1524#L215

I remenber seeing this a while ago and said this could break something but couldn't find a logical solution, now I have it if SA changes it's api (as happen with 1.0-2.0) and TG hasn't migrated then if someone install the lastest SA, well what your having :)

fortunate for you Max notice this too and commited a patch http://trac.turbogears.org/turbogears/changeset/1523

not the prettiest but it works :)

so you have two way, #1 get the lastest 1.0 branch (trunk may have unstable features) or uninstall SA.

Seriously this is weird how could TG know about SQLAlchemy unless
something happens during easy install?

because when SA code was added it was intended to become the main ORM, it still is but it isn't clear how to migrate in a proper way.

how about using extras_require in setuptools? and a config file entry in app.cfg maybe?

I registered a metadata but that was it.  Somebody hack my machine?

hehehe well yes, someone trip you into installing a peace of malware call turbogears that coerce itself to run code on top of SQLAlchemy :)



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