Changelog for persistent-mysql-2.6.2
2.6.2
- Extend the
SomeFieldtype to allowinsertManyOnDuplicateKeyUpdateto conditionally copy values. - Depend on
mysql-simple >= 0.4.3to fix encoding and decoding of date/time values with fractional seconds (when a column is specified using something likesqltype=TIME(6)). See also #705 - Fix behavior of
insertManyOnDuplicateKeyUpdateto ignore duplicate key exceptions when no updates specified.
2.6.1
- Add functions
insertOnDuplicateKeyUpdate,insertManyOnDuplicateKeyUpdatetoDatabase.Persist.MySQLmodule.
2.6.0.2
Prevent spurious no-op migrations when default=NULL is specified - revised version #672 (which fixes bug #671 introduced by the earlier attempt #641)
2.6
Compatibility for backend-specific upsert functionality. A lucky contributor could add upsert to the MySQL backend now, i.e.: INSERT ... ON DUPICATE ...
2.5
- changes for read/write typeclass split
2.3.0.1
Support usign default= for changing the id field type
2.3
- Distinguish between binary and non-binary strings in MySQL #451
- Previously all string columns (VARCHAR, TEXT, etc.) were being returned from Persistent as
PersistByteStrings (i.e. as binary data). Persistent now checks character set information to determine if the value should be returned asPersistTextorPersistByteString. - This is a breaking change if your code is relying on a
PersistByteStringbeing returned for string-like MySQL values; persistent-mysql itself had several runtime errors that needed to be fixed because of this patch. High-level code dealing purely withPersistEntitiesshould be unaffected.
- Previously all string columns (VARCHAR, TEXT, etc.) were being returned from Persistent as
2.2
- Update to persistent 2.2
2.1.3
- Added a
Showinstance forMySQLConf.
2.1.2.1
Documentation typo fix
2.1.2
Provide a FromJSON instance for MySQLConf.