I asked on the #dbix-class irc channel and got this reply: castaway: dbic does not do it, the dbd backend does (quote numerics that is) iirc you may have to figure out bind_params.. I know theres a patch/thing for bind_params for PGs bytea, but not about numerics [also look in ::Storage::DBI::Pg for blob stuff iirc theres a pg-specific thing for that too
On Tue, Apr 15, 2008 at 7:57 AM, <[EMAIL PROTECTED]> wrote: > > > > Hi, > > I've taken the plunge and am attempting to grok DBIx::Class, with respect to > Sybase. 2 bugs are hindering my progress. The latter has got me at a pause. > I know in one of the Catalyst/DBIx::Class presentations given (I think it > was Robert's?), a solution was provided for it. > > 1. Sybase goes nanners when you try to quote a numeric in a where clause. > DBIx::Class seems to insist on doing this. So for instance, column XXX is > numeric, so in my DBIC code I have: XXX => 5 for my search criteria. But > DBIC wants to execute the following SQL: where XXX = "5". This makes Sybase > complain that I can't do the comparison without an explicit convert call. > I'm working around this by doing a really ugly thing in DBIC code: XXX => > \' = 1'. > > 2. The real stumper is automatically decoding a blob value and inflating it > into the column. At the moment, I'm just stabbing at it. Can someone give me > an example of how to accomplish this? > > Thanks, > Todd > > ________________________________ > > > > > Generally, this communication is for informational purposes only and it is > not intended as an offer or solicitation for the purchase or sale of any > financial instrument or as an official confirmation of any transaction. In > the event you are receiving the offering materials attached below related to > your interest in hedge funds or private equity, this communication may be > intended as an offer or solicitation for the purchase or sale of such > fund(s). All market prices, data and other information are not warranted as > to completeness or accuracy and are subject to change without notice. Any > comments or statements made herein do not necessarily reflect those of > JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may > contain information that is privileged, confidential, legally privileged, > and/or exempt from disclosure under applicable law. If you are not the > intended recipient, you are hereby notified that any disclosure, copying, > distribution, or use of the information contained herein (including any > reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any > attachments are believed to be free of any virus or other defect that might > affect any computer system into which it is received and opened, it is the > responsibility of the recipient to ensure that it is virus free and no > responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and > affiliates, as applicable, for any loss or damage arising in any way from > its use. If you received this transmission in error, please immediately > contact the sender and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. Please refer to > http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK > legal entities. > _______________________________________________ > Houston mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/houston > Website: http://houston.pm.org/ > _______________________________________________ Houston mailing list [email protected] http://mail.pm.org/mailman/listinfo/houston Website: http://houston.pm.org/
