Changelog for persistent-mysql-2.6.0.1
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
PersistByteString
s (i.e. as binary data). Persistent now checks character set information to determine if the value should be returned asPersistText
orPersistByteString
. - This is a breaking change if your code is relying on a
PersistByteString
being 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 withPersistEntities
should 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
Show
instance forMySQLConf
.
2.1.2.1
Documentation typo fix
2.1.2
Provide a FromJSON
instance for MySQLConf
.