Hi John - I just tried out your implementation - it works great for me, 
thanks!  (and I like that it is not specific to Oracle anymore)

As for Sequel being able to pass down the CLOB type, I'm at a loss too, 
although my experience with Sequel in general is very limited.  In the 
rails migration I posted, line #7 "t.text :doc, :null => false", the 'text' 
type translates to CLOB automatically.  Note that this migration is being 
used in an activerecord environment, so the translation is being handled by 
the 'activerecord-oracle_enhanced-adapter' gem.  We are using activerecord 
with oracle throughout our rails app, and just introducing Sequel for ruote 
workflow purposes.  Not sure how that migration would be translated in a 
pure Rails / Sequel environment.  So perhaps just documenting a rails 
migration comment would be good enough for now?  And/or as you suggest, a 
SQL snippet for creating your table/indexes in Oracle.

Thank you again for your good support,
Geoff

On Thursday, September 20, 2012 5:45:55 PM UTC-4, John Mettraux wrote:
>
>
> On Wed, Sep 19, 2012 at 08:34:46PM -0700, gmh wrote: 
> > 
> > Hi John - thank you for your quick reply.  Awesome! - your suggested 
> > solution is similar to what I did to get things to work for us: 
> > https://gist.github.com/3753803 
>
> Hello Geoff, 
>
> I digested the read detection and the decoding into one method: 
>
>   
> https://github.com/jmettraux/ruote-sequel/commit/e5aaf9bb01edddde238c1ed3a796d0039160bcd1
>  
>
> It should thus accomodate strings and whatever has a #read method (adapt 
> to 
> more databases than just Oracle and its driver). 
>
>
> > But you are right, the 'create_table' code is still broken.  Since we 
> > wanted more control over the table creation process in Rails, I created 
> a 
> > migration (https://gist.github.com/3753821) instead of using your 
> > 'create_table' method, so that will still need to be addressed. 
>
> I've tried to look for ways to specify the :db_type when using Sequel's 
> create_type, but couldn't find one. 
>
> Does your ActiveRecord migration specify CLOB by itself? There is nothing 
> except 
> :text => true. 
>
> One thing I could do is pass the info in the documentation (the readme), 
> if 
> the ActiveRecord migration gracefully produces a CLOB column, I could pass 
> it 
> (with due credits) or maybe as an Oracle SQL snippet directly. 
>
>
> What do you think? 
>
> -- 
> 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

Reply via email to