I have used Roundcube for awhile now and it works great... :)
But I see you say that the DB should use UTF-8, any reasons for this? ( I have never used UTF-8 for the db and never had any problems...)
Also, when upgrading from an old version, there is nothing in the db that I need to preserve? I can start with a fresh db without loosing anything? (except for address book?)
Regards,
BTJ
The reason why UTF-8 is recommended is because other formats can have problems with other character sets, for example: http://www.roundcubeforum.net/5-release-support/17-pending-issues/8621-problem-sending-e-mails-attached-files-german-umlaut-filename.html so I guess the question is why wouldn't you want to use UFT-8? Off the top of my head I can't think of any critical information that is kept the database other than the contacts, contact groups, account preferences, and plugin data so I other than that I think you could start with a fresh DB, but as always backup the database before the upgrade.
The reason is that we still use ISO-8859-1 as our encoding and haven't found a good enough reason to change it yet... :)
btw, can I keep the db and upgrade from 0.4.x to 0.8.x? (I see there is much info in the db, contact, identities and contactgroups that our users seems to be using? Or can I insert the old data using sql insert after starting with a fresh db?
BTJ
You can keep the current database just run the mysql queries below your current version in the sql upgrade file.
I don't use MySQL but found it, thx... :)
BTJ
Sorry I tried to not be database specific ("current version in the sql upgrade") but it sliped out, out of curiosity what are you using?
I only use the best, PostgreSQL... ;)
BTJ
Interesting to see another happy PostgreSQL user, not all that happy with MySQL lately and considering switching. Out of curiosity do you have a large user base on PostgreSQL?
Not so large userbase using Roundcube... But I am a developer and I have been using PostgreSQL on all my/our projects the last 10 years... :)
And btw, if you are worried that PostgreSQL can't handle the load don't be... It's built to handle lots of data.... :)
BTJ
We use postgres for RC with a few hundred thousand users in the DB.