You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I am porting a rails project from rails 2.3.x to rails 3.2.x. We are using spatial oracle, but the rails project itself is not inserting SDO_GEOMETRY. For now we use either stored procedures or specific gis software to create and update new spatial data --the rails process just handles the administrative data.
So I want to just create a new row with the SDO_GEOMETRY set to zero, which for the moment is not possible. Somehow the default behaviour converts the NULL value to a string? (I deduced that from the error).
I did see #268 but for now I would prefer a solution which would make sure there are no errors, and later when I want to manage SDO_GEOMETRY, create a gem that will handle it completely correctly (and using rgeo).
In #268 I did see @kubo refering to a gist, so I'll see if I can extract something minimal that could help (I don't quite understand the gist just yet 😄)
The text was updated successfully, but these errors were encountered:
For now I was able to find an easy solution, by using ignore_table_columns, since I am not inserting any data into the geometry column for now.
In a later stage in my current project I will definitely need to create geometries from within the rails process, and at that time I will dive into the outdated spatial-adapter fork, and write an rgeo oracle adapter. Then I will be able to integrate @kubo's gist correctly 😃
Hi there, I am porting a rails project from rails 2.3.x to rails 3.2.x. We are using spatial oracle, but the rails project itself is not inserting
SDO_GEOMETRY
. For now we use either stored procedures or specific gis software to create and update new spatial data --the rails process just handles the administrative data.So I want to just create a new row with the
SDO_GEOMETRY
set to zero, which for the moment is not possible. Somehow the default behaviour converts the NULL value to a string? (I deduced that from the error).I did see #268 but for now I would prefer a solution which would make sure there are no errors, and later when I want to manage
SDO_GEOMETRY
, create a gem that will handle it completely correctly (and using rgeo).In #268 I did see @kubo refering to a gist, so I'll see if I can extract something minimal that could help (I don't quite understand the gist just yet 😄)
The text was updated successfully, but these errors were encountered: