Skip Menu |
 

This queue is for tickets about the DBIx-Class CPAN distribution.

Report information
The Basics
Id: 87154
Status: rejected
Priority: 0/
Queue: DBIx-Class

People
Owner: Nobody in particular
Requestors: jonathan.stowe [...] db.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: missing text lob type in DBIx::Class::Storage::DBI
Date: Mon, 22 Jul 2013 16:43:07 +0200
To: "'bug-DBIx-Class [...] rt.cpan.org'" <bug-DBIx-Class [...] rt.cpan.org>
From: Jonathan Stowe <jonathan.stowe [...] db.com>
Download (untitled) / with headers
text/plain 1.1k
Classification: Public Hi, In DBIx::Class::Storage::DBI the method _is_lob_type has $data_type && ($data_type =~ /lob|bfile|text|image|bytea|memo/i And the _is_text_lob_type has $data_type && ($data_type =~ /^(?:clob|memo)\z/i Whereas I suspect that it should be: $data_type && ($data_type =~ /^(?:clob|memo|text)\z/i On Oracle assuming that we have relied on SQL::Translator to do translate a column defined as "text" to "clob" in the schema (which it does, ) this will result in: DBI Exception: DBD::Oracle::st execute failed: ORA-00932: inconsistent datatypes: expected CLOB got BLOB.. because the ora_type is being set incorrectly in the bind_params in DBIx::Class::Storage::DBI::Oracle::Generic (it defaults to ORA_BLOB .) Thanks. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Download (untitled) / with headers
text/plain 812b
On Mon Jul 22 10:43:29 2013, jonathan.stowe@db.com wrote: Show quoted text
> Classification: Public > > > Hi,
Hi, sorry for the late reply Show quoted text
> > On Oracle assuming that we have relied on SQL::Translator to do > translate a column defined as "text" to "clob" in the schema (which it > does, ) this will result in:
I am not sure what you mean here... How does SQLT influence the data type definitions in your Result class? The reason 'text' is not included in the generic DBI driver is because it is *exceedingly* broad, and means ifferent things on different engines. I much rather not set a precedent by mapping it to CLOB (or should it be NCLOB? trick question!), but instead have the user supply the correct data type for the engine in question. I am open to be swayed if you outline your use-case in more detail. Cheers
Download (untitled) / with headers
text/plain 260b
No reply to follow up question for about 6 months. I am rejecting the ticket for the time being, please feel free to reopen it if you still think action needs to be taken ( outstanding questions at https://rt.cpan.org/Ticket/Display.html?id=87154#txn-1255270 )


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.