You can use symfony to export your current schema to a schem.yml file. However, before you build models from that schema file, you can add php name attributes to each table and column. This way the tables and columns with horrid names can all be referred to be more understandable and consitant names in code.
On Wed, Nov 3, 2010 at 10:24 AM, brillenfux <[email protected]>wrote: > Hi, > > I have to integrate a very bad legacy database and I'd have to specify > things in the model extensively. There are fields (like contact_id) > that are named inconsistently all through the database for example > (like contact, contactid, Contact, Kontakt, KontaktID etc.) also there > are fields with random names (like "ext" which is in fact a group_id > field). > How many of the field references in the code etc are hard-coded? How > extensively can I design the model. What obstacles will I see? > Is there a something comprehensive to read about that topic? > > Thanks, > Enno > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-users%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en
