Re^3: Class::DBI and MySQL ENCODE/DECODE

Didn't you just say you want encode/decode everything for this table? If you override these in one class/table, it will not affect any others.

Comment on Re^3: Class::DBI and MySQL ENCODE/DECODE

Replies are listed 'Best First'.
Re^4: Class::DBI and MySQL ENCODE/DECODE by Anonymous Monk on Dec 23, 2005 at 05:03 UTC
I didn't mean to say that the entire table is encoded, although it looks like what I did say could be read that way. I thought I had said only some columns were encoded. So a straight query might be something like: SELECT a, b, DECODE(c, 'foo') AS c FROM mytable The problem being that not all columns are encoded - otherwise rewriting the fragments would be perfect. Sorry about any confusion caused.	[reply]
Re^5: Class::DBI and MySQL ENCODE/DECODE by perrin (Chancellor) on Dec 23, 2005 at 18:05 UTC
I would try the get/set route then, if duplicating encode in perl is not too bad.	[reply]