data types - no st_point, only point
Closed this issue · 2 comments
Hi, I'm brand new to this adaptor, so I might be getting something wrong - but it appears when you use the st_point data type for a column in a migration, the migration throws an undefined method error for st_point, but point works just fine. Is the correct data type for a point now point and the docs are outdated, or are point and st_point distinct data types?
2.n uses point
3.beta use st_point. To get st_point you have to update your gemfile to
reference the current beta.
In other words, yes, docs will need updating.
M
On Sun, Mar 1, 2015 at 1:53 AM, Anthony Goddard notifications@github.com
wrote:
Hi, I'm brand new to this adaptor, so I might be getting something wrong -
but it appears when you use the st_point data type for a column in a
migration, the migration throws an undefined method error for st_point,
but point works just fine. Is the correct data type for a point now point
and the docs are outdated, or are point and st_point distinct data types?—
Reply to this email directly or view it on GitHub
#169.
awesome, makes perfect sense now, thanks!