I'm cross-posting this to the DBIx::Class and the Catalyst mailing list as both users might be interested in it.
I wanted to do this as soon as I've read the first blog post about the ExtJS 4 data model and last Friday evening I've finally started writing it. After a short discussion on #dbix-class on Friday I chose to implement it as a SQL::Translator Producer so other ORM frameworks could just write a SQL::T::Parser and use it too. Personally I'll use the generated ExtJS classes with Catalyst::Controller::DBIC::API in the backend. The one drawback of making it a sqlt producer is that the dbic parser loses the relationship names when creating the sqlt constraints. This means that for using the resulting ExtJS classes with DBIC::API the user has to change all relationship names. What's your opinion on this issue? Should it be a different module that directly parses dbic resultsources instead of using sqlt? The code is hosted on github: https://github.com/abraxxa/SQL-Translator-Producer-ExtJS-Model-File Best regards, Alex (abraxxa) *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien Handelsgericht Wien, FN 79340b *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* Notice: This e-mail contains information that is confidential and may be privileged. If you are not the intended recipient, please notify the sender and then delete this e-mail immediately. *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
