Carl Karsten wrote:
>>> I am working with django (python web framework
>>> http://djangoproject.com) which "works best" if you define your data
>>> like this:
>>
>> [snip]
>>
>>> problem is the django class code supports more than what Workbench
>>> supports. see: http://www.djangoproject.com/documentation/model-api/
FWIW, there's a similar situation with Perl's DBIx::Class (often used
with Catalyst) where the model contains information that's not needed or
present in the RDBMS. The SQL::Translator module helps a bit.
Alfredo Kojima wrote:
>> A couple of notes:
>>
>> 1- Workbench has a powerful plugin system, which includes support for
>> Python.
<snip>
>> 2- We're currently refactoring the Workbench a great deal
<snip>
>> 3- There is some preliminary info on writing plugins at
>> http://forge.mysql.com/wiki/MySQL_Workbench_Plugins and
>> http://forge.mysql.com/wiki/MySQL_Workbench
I notice that the list doesn't include Perl and that although C is
mentioned, there's no detail, which would make it difficult to write an
interface using XS. Are there plans to support Perl in the new version?
Cheers, Dave
