Message6231
My fix for CSV import/export compatibility also includes some changes to
make the journal representation in RDBMS databases with Python 3
compatible with that used with Python 2. Given that, some limited
testing indicates sqlite databases are compatible between Python
versions (including with non-ASCII characters in the main data and the
journal), *if* you delete db/otks and db/sessions (anydbm files) when
changing Python version. anydbm databases are not compatible and
probably can't be compatible.
It's plausible that, given those changes, mysql and postgresql databases
are also compatible (including with non-ASCII characters), but that
still needs to be tested. |
|
Date |
User |
Action |
Args |
2018-09-02 23:55:46 | joseph_myers | set | messageid: <1535932546.37.0.56676864532.issue2550975@psf.upfronthosting.co.za> |
2018-09-02 23:55:46 | joseph_myers | set | recipients:
+ joseph_myers, rouilj |
2018-09-02 23:55:46 | joseph_myers | link | issue2550975 messages |
2018-09-02 23:55:45 | joseph_myers | create | |
|