Hi John - as suggested, I created a small test case and passed it on to the Sequel developer: https://github.com/jeremyevans/sequel/issues/557#issuecomment-8939069
Also, I modified ruote-sequel according to his suggestion. https://github.com/gherney/ruote-sequel/commit/3987c56424771d54eaca7d68e8f0964f8fe71681 As you can see, it is not the cleanest solution, but perhaps you can come up with a more generic implementation? Thanks for your good support, Geoff On Thu, Sep 27, 2012 at 4:32 PM, John Mettraux <[email protected]> wrote: > > On Thu, Sep 27, 2012 at 06:29:37AM -0700, gmh wrote: > > > > error class/message/backtrace: > > Sequel::DatabaseError > > "OCIError: ORA-01704: string literal too long" > > stmt.c:235:in oci8lib_191.so > > > > This seems to be related to the way Sequel is creating the INSERT. I am > > able to trigger the same error using the Oracle SQL Developer tool, > feeding > > in the SQL produced by the Sequel gem. > > Hello Geoff, > > so if I understand you correctly, the "doc" column is correctly mapped to a > CLOB, but is limited to 4000 chars. > > That's worth trying to reproduce in a few lines of Ruby + Sequel and being > reported to the sequel issue tracker / mailing list of Sequel. > (Sorry I cannot do it for you, I have no access to an Oracle DB similar to > yours). > > That'd be great if you took the time to do that. > > Cheers, > > -- > John Mettraux - http://lambda.io/jmettraux > > -- > you received this message because you are subscribed to the "ruote users" > group. > to post : send email to [email protected] > to unsubscribe : send email to > [email protected] > more options : http://groups.google.com/group/openwferu-users?hl=en > -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
