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
There is a related issue at jashmenn/activeuuid#70 - but as of yet I haven't received any advice on that on that end.
ActiveUUID provides a binary(16) field for databases that don't natively support UUIDs. In my case, MySQL. I'm trying to port to PostgreSQL, which does have support for UUIDs.
While PostgreSQL, in my tests, exports using the '00110954-44a5-4ce2-b067-3cf26a9ea631' format.
I've tried patching ActiveUUID, but nothing I've done seems to effect the export - I've assumed I needed to implement UUIDTools::UUID.to_yaml ... or dump, or somthing.
Any suggestions as to what need to be implemented to change the export format?
The text was updated successfully, but these errors were encountered:
There is a related issue at jashmenn/activeuuid#70 - but as of yet I haven't received any advice on that on that end.
ActiveUUID provides a binary(16) field for databases that don't natively support UUIDs. In my case, MySQL. I'm trying to port to PostgreSQL, which does have support for UUIDs.
When a record looks like this:
MySQL exports like this:
While PostgreSQL, in my tests, exports using the '00110954-44a5-4ce2-b067-3cf26a9ea631' format.
I've tried patching ActiveUUID, but nothing I've done seems to effect the export - I've assumed I needed to implement UUIDTools::UUID.to_yaml ... or dump, or somthing.
Any suggestions as to what need to be implemented to change the export format?
The text was updated successfully, but these errors were encountered: