> Is SC's underlying db code getting a little long in the tooth? We've Not in the case you mention. It was related to encoding - something which touches all and everything in our code (path, file names, settings, web interface, values stored in the DB etc.).
> been through hash->SQLite->MySQL now and I'm wondering if what we've That particular case even dated back from SQLite times. And it would have been broken in the hash times, too. > got here under the hood is spaghetti code, especially given DBI's level > of abstraction. Is it time to at least start considering a db-refactor > branch and effort? This is definitely something we'd like to see for SC8. Though the spaghetti code metaphor doesn't fit in with the OO DB abstraction ;-) -- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
