Rails - Oct 2005 - Empty fields and Oracle CLOBs

I have a field that is a clob within an Oracle database on Rails
0.13. Things have been working well until I tried to submit the field
empty via a rails app at which point the following error was
returned:

ORA-24801: illegal parameter value in OCI lob function
/app/controllers/publications_controller.rb:64:in `update''

The line in question was:
if @publication.update_attributes(params[:publication])

The field in question was created with the following SQL:
ABSTRACT	CLOB DEFAULT NULL,

Is this a rails error talking to Oracle or is it a misconfiguration
on my end?


		
___________________________________________________________ 
How much free photo storage do you get? Store your holiday 
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Oct 4, 2005, at 5:02 AM, Sitsofe Wheeler wrote:
> I have a field that is a clob within an Oracle database on Rails
> 0.13. Things have been working well until I tried to submit the field
> empty via a rails app at which point the following error was
> returned:
>
> ORA-24801: illegal parameter value in OCI lob function
> /app/controllers/publications_controller.rb:64:in `update''
>
> The line in question was:
> if @publication.update_attributes(params[:publication])
>
> The field in question was created with the following SQL:
> ABSTRACT    CLOB DEFAULT NULL,
>
> Is this a rails error talking to Oracle or is it a misconfiguration
> on my end?
It''s likely a problem with the ActiveRecord OCI adapter.
Please file a ticket at http://dev.rubyonrails.org/newticket

Best,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDQqlpAQHALep9HFYRAorBAKCn+X7hi5R8eWMfnvUSFk+yS7DozQCg0eaW
1qym6lYU7MtRaS0DnaagxNY=NmoS
-----END PGP SIGNATURE-----

Jeremy Kemper wrote:
> It''s likely a problem with the ActiveRecord OCI adapter.
> Please file a ticket at http://dev.rubyonrails.org/newticket
After filing a bug (http://dev.rubyonrails.org/ticket/2383 ) and 
producing a fix, I flipped through the online source and noticed that it 
has already been fixed in 0.13.1 by 
http://dev.rubyonrails.org/ticket/1807 via 
http://dev.rubyonrails.org/ticket/1798 .