Best solution for custom / unplanned fields in database? |
[eluser]Skinnpenal[/eluser]
Thanks for your reply, xzela. Now I know not to mess with the database ![]() Another solution could be to have a table per field type. I think Concrete5 uses this approach. The downside of that would be that each page would potentially require tons on joins to get all the data out. And a little less convenient to develope, as aposed to just putting it all in one table. |
Messages In This Thread |
Best solution for custom / unplanned fields in database? - by El Forum - 05-22-2009, 03:34 AM
Best solution for custom / unplanned fields in database? - by El Forum - 05-22-2009, 06:49 PM
Best solution for custom / unplanned fields in database? - by El Forum - 05-23-2009, 04:20 AM
Best solution for custom / unplanned fields in database? - by El Forum - 05-23-2009, 04:46 AM
|