[Database structure compatibility] Branch update: From 1.x to 2.x

If you have questions about using mojoPortal, you can post them here.

You may want to first review our site administration documentation to see if your question is answered there.

This thread is closed to new posts. You must sign in to post in the forums.
7/26/2006 7:58:42 PM
Alexander Orlov
Gravatar
Total Posts 23
View Posts

[Database structure compatibility] Branch update: From 1.x to 2.x

When ASP.NET 2 will be completly implemented in Mono the 1.x branch will disappear. Will it be possible simply to update MP by updating the files in die MP dir and eventually apply some script.sql files to update the database structure?

OR: Will it be necessary to create a completly new database?

P.S.: Joe, I don‘t how it‘s under Windows but under Linux „Alt + Xnum“ is the default shortcut for switching tabs (Firefox). E.g.: „Alt + 3“ for the third tab and so on... So Linux users can‘t use the accesskeys.
7/27/2006 8:01:02 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: [Database structure compatibility] Branch update: From 1.x to 2.x

Yes, the db schema for 1.0.1 and 2.0.1 is identical so any mojoportal site upgraded to 1.0.1 or higher will be able to upgrade the db starting with the script for 2-01to2-1, since no schema changes have happened in 1.x since 1.0.1

Keeping this upgrade path is why we shouldn't change the schema in the 1.x branch going forward.

I didn't know about the Alt xnum keys in Linux Firefox. it is not that way in Windows. I chose numbers for the access keys specifically based on the recommendation to use numbers so that it would not interfere with access keys for browsers.

I guess what I need is a list of keys that I can use without conflict.

Joe
You must sign in to post in the forums. This thread is closed to new posts.