Closed saulortega closed 6 years ago
Hmm. v3 shouldn't be that broken... There were some fixes contributed recently so it should be working? There shouldn't be any imports missing for tests. Though yes, postgres -> psql was a breaking change.
I'd hope that we could put the Point
type into the sqlboiler types
package. No real extra comments except for that until I see the real code :)
Sure. But, should we create a subpackage for these types? Because other databases with the same types work differently, so foreseeing a future implementation for Mysql (or other) it must be taken into account that the Point type of Mysql is different than the Point type of Postgres.
Sure thing.
Closing this in favor of the PR #263
It was not easy to try it in v3. It's very broken! ("postgres" changes to "psql", missing ALL imports in main_test.go, and so on...)
But in the end I succeeded. :)
Well, before doing PR, I want to show here the changes that would be added to the code, and to know your opinions. For now, I did tests with the point type. These same changes should be made for the other geometric types.
OK, the point type: https://github.com/saulortega/pgeo/blob/master/point.go
randomize/randomize.go:
importers/imports.go:
drivers/sqlboiler-psql/driver/psql.go:
That is all.
What do you think, Aaron?