Matthew O'Connor wrote: > So what do all the users who's databases aren't in SQL_ASCII supposed to > do? Any why not convert those columns to bytea now? I think it's > better to byte the bullet now (sorry about the pun) and wait a few more > weeks rather than push out the 2.2 release too soon.
dbmail-pgsql has never been supported on charsets other than sql_ascii. Fixing this properly for all the caching tables will take more than just a change of the schema. Releasing 2.2 will not be delayed until then. > > BTW, I'm willing to help if I can, I can write up the SQL script to > convert all the relevant columns if you bytea if you would like? Fixing this on the trunk will be a priority goal. Doing it on the trunk will give us a proper timeframe for impact assessment and testing. If it turns out to be a limited change, it will be merged into the stable 2.2 tree. I'm sorry I can't offer you more than that. Delaying 2.2 is not an option, and the 2.2 branch is in deep freeze at the moment. > > Matt > > > Paul J Stevens wrote: >> I have not fully reverted to 2.1.7 behaviour. >> >> Postgresql users will have to use SQL_ASCII encoding until we migrate al >> relevant columns to bytea. >> >> This will be done, but not in 2.2 >> >> >> >> Paul J Stevens wrote: >>>> So, koi8-r text is inserted into dbmail_headervalue with convertion >>>> to utf >>>> and to dbmail_envelope "as-is" >>>> Is this as expected? >>> No. I've removed one last remaining conversion to utf8 outside of the >>> pgsql driver. >>> >>> >> > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
