Re: [announce] OPiuM -- stock Options Portfolio Manager

> I have to say I'm very displeased with the whole way I *had* to build the > database. It seems to me that security in databases should be paramount, and > the ENCODE/DECODE functions feel like an afterthought. Like, "oh yeah, let's > just slap this stuff in and have it only work on strings!". I would love to They don't only work on strings, it's just that they return strings. While the extension you mentioned would be interesting, it would also completely break things like indexes and queries. I think you're trying to put too much in the database. Another approach would be to define objects for all of your records, use serialize() to turn each object into a string (which could be encoded using the mcrypt functions) and store that. Once you retrieve that object back, use unserialize() to restore it.