Paul J Stevens wrote:
Tommi Lätti wrote:
Does the migrate2.0_2.2 script make so that the database is then
unusable for 2.0 series?
Check the text->bytea conversion of dbmail_messageblks.messageblk, the
first transaction block at the top of the migration script. That's the
only *real* change that makes imapd-2.0 choke on a the database.
I'm not sure if the data it's in bytea already. Schema is from 2.0.9, I
imported the data to that schema. I could of course try putting 2.2.1
schema on and then importing the data to that.
The tricky question is that I don't really remember how far the migrate
script went. But since the bytea conversion is at the top, I could
safely assume that it's definitely converted at least some amount of
messageblocks, if not all.
Can I cast them back to text? Or should I try to run the migrate script
again to get the new tables and then dbmail-util -ay from 2.2.1?
-- clip --
The log-file actually looks clean, but the client will choke on the
conversion issue.
Allrighty, I could check that with tcpdump maybe but I think I can
assume that it's now bytea... although the schema says text.
(damn I always try to send from wrong address first and the the mailing
list puts the mail on hold. Sorry for the duplicates if they pop up.)
--
br,
Tommi
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
