Hello, Unfortunately, we haven't done any experiments with MySQL's GIS implementation yet, so there might be some caveats. I'm sure you can work around any caveat by using jOOQ's plain SQL capabilities, but it would still be nice to have some out-of-the-box integration.
I'll experiment with that some time next week. If you have any findings, we'd be very happy to learn about those as well. Best Regards, Lukas 2015-01-03 16:48 GMT+01:00 <[email protected]>: > Thanks for the quick response! > I am actually using MySQL for now, but I guess it should work as well with > custom data type bindings. > But I am also thinking of switching to PostgreSQL since PostGIS seems far > superior to MySQL's spatial functionality. It depends on the effort of > refactoring the code. > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
