On May 23, 9:18 am, "Benjamin A. Shelton" <zancar...@gmail.com> wrote:
> As an addendum to my previous posts, here is a run-through on my
> solution for anyone who might encounter a similar problem at a future
> date.
>
> First, I tried using metaclasses to resolve the issue of having to
> tack on a __tablename__ to each object in my app's model. This didn't
> work, and I found out why. In SQLAlchemy, the declarative_base()
> function returns a class that itself is already generated from a
> metaclass. The result is that you're left with an error message (one
> that is almost comical if you imagine it spoken as a sage's riddle)
> along the lines of:
>
> metaclass conflict: the metaclass of a derived class must be a
> (non-strict) subclass of the metaclasses of all its bases
Perhaps the recipe "Recipe 204197: SOLVING THE METACLASS CONFLICT"
might be of help:
http://code.activestate.com/recipes/204197/
Kind regards,
Jasper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to turbogears@googlegroups.com
To unsubscribe from this group, send email to
turbogears+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
