I am working with django (python web framework http://djangoproject.com) which "works best" if you define your data like this:

class Poll(models.Model): question = models.CharField(maxlength=200) pub_date = models.DateTimeField('date published')

class Choice(models.Model): poll = models.ForeignKey(Poll) choice = models.CharField(maxlength=200) votes = models.IntegerField()

Then you use a utility to read that and issue the CREATE TABLE commands to the db server. It 'can' use an existing db, but the "best practices" seem to be to use the class definitions to be the primary location of model definition, and use them to drive the db structure definition.

In the past, I have used my data modeling tool (like MySql Workbench) as the primary. I am hoping to continue. What I envision is using Workbench to define my model, then somehow generate the class code. The problem is the django class code supports more than what Workbench supports. see: http://www.djangoproject.com/documentation/model-api/

So, before I got looking at the xml that Workbench uses to represent a model or any other such fun, has anyone started down this path?