Welcome Guest, Not a member yet? Register   Sign In
Best solution for custom / unplanned fields in database?
#3

[eluser]Skinnpenal[/eluser]
Thanks for your reply, xzela. Now I know not to mess with the database Smile

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-23-2009, 04:20 AM



Theme © iAndrew 2016 - Forum software by © MyBB