Hi, I've been working on this patch to allow bind parameter attributes so that we can properly support column types like Oracles B/CLOB type or Postgres' BYTEA type and wondering if there is a need to set the attributes for selects and deletes. I have this working (for me :) ) for inserts and updates, which I think is the primary use case to allow people to insert and update these troublesome column types, but I can't think of a use case for deletes or selects.
If nobody needs this I'd rather leave it be for now, since this patch already makes changes to important functions like ...DBI->_execute and ...Row->update|insert (in other words methods that everyone uses all the time) and I'm trying to minimize the invasiveness of my change in order to improve the chances of it being accepted :) Also if there are other people out there that are interested in this, please let me know since I'd like someone who needs it for Oracle to help test and see if it works. Thanks! John ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $510k for $1,698/mo. Calculate new payment! www.LowerMyBills.com/lre _______________________________________________ List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class Wiki: http://dbix-class.shadowcatsystems.co.uk/ IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/ Searchable Archive: http://www.mail-archive.com/[email protected]/
