There is a problem with blobs in ActiveRecord when you''re using
sqlite3: sql length limits. Sqlite3 limits the size of the sql
queries to 1mb. Because AR puts everything into the sql text, you
can''t insert a blob or a clob that is larger than about a meg.
That sucks.
So I''m trying to fix that, but there''s a problem (obviously,
or I
wouldn''t be here...). The sql is created before it gets to the
sqlite3 adapter. That means that I would have to parse the sql text
to pull out the data fields. I would also have to un-escape all that
data.
Is there something I''ve missed? Some way to override the behavior of
create and update w/o changing the relationship between
ActiveRecord::Base and the connection adapter?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
