Storing a great many fields in a database

[Mark Wieder]

Doc-

Saturday, July 14, 2012, 3:16:25 PM, you wrote:

> Or split it into two tables, and let my get/set functions figure out
> which to use, one for currency values, and the other for everything
> else?

OMG. You have that many fields in *one* table? I think you need a
serious database redesign. Or "design", since it sounds like it was
never really designed in the first place. Come up with a database
schema, split the data into component tables, and this will all become
much easier.

-- 
-Mark Wieder
 mwieder at ahsoftware.net