Hi, In my opinion you should really create a virtual schema as the previous poster mentioned. Create one table "Table" that stores the custom tables, one table "Field" for the field definitions (like display name, type, default value etc.), one table "TableEntry" for the virtual objects and one table "FieldValue" for the values of the virtual fields.
A colleague of mine did this in his open-source project "Ullright" which is a available at http://ull.at. I suggest to look at its source if you want to know more. Bernhard -- Sent from my HTC Hero 7. Aug 2009 11:56 vorm. schrieb am "cosmy" <c.zec...@gmail.com>: Ok, i think it could be a solution but.. how do i manage the persistence of this data? In other words, how do i save the data of these forms in the database? Maybe as an unique string in a specific table ( in example: [attribute: value | attribute2: value2] ) ? but how do i manage the queries? i have to use LIKE or regexp and it will be very slow to get out data of a specific type of entry, won't it? Is there an api of symfony to manage this kind of things? On 7 Ago, 08:22, Alan Bem <alan....@gmail.com> wrote: > You shouldn't change database schema on "li... > On Fri, Aug 7, 2009 at 5:50 AM, Alan Candido <bro...@gmail.com> wrote: > > Hi, > > > I don't tried... > > 2009/8/3 cosmy <c.zec...@gmail.com> > > >> Hi all, > >> I need to realize an application that let the possibility to make > >> dynamic ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
