• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!
  • 2026 staff recruitment is open! Check it out and consider applying!

AAC Database change 0.4 -> 1.3? its possible?

roriscrave

Advanced OT User
Joined
Dec 7, 2011
Messages
1,210
Solutions
35
Reaction score
207
Hi, i have my server online about 3 months, and i'm changing my source code 0.4 to 1.3..
is possible to change a database 0.4 -> 1.3 whitout loss all? i tried and get a lot of errors.
Thx!
 
It is possible with a migration routine. Basically a script that parses the old 0.4 database, converts the values to be compatible with the new 1.3 database and populates it.

I have written something similar, database2znoteaac loads a database and populate the neccesary znote_ tables so the database is compatible with Znote AAC, no matter which original AAC was used. Znote AAC also supports multiple databases, and has the query differences between TFS 0.4 and 1.3 for all kinds of tasks.

But a script that loads a populated 0.3/4 database, converts and imports it into a 1.3 database is significant work. Takes much time to develop and test, not to mention it requires a populated 0.3/4 database for testing. So its not something everyone can easily do.

I imagine it might be possible to do entirely in SQL using multiple temp tables.

With basic CRUD knowledge in any language and deep understanding of the database anyone can do it.
With advanced SQL knowledge you can do it efficiently with only SQL code.

So yes, it is possible.
 
It is possible with a migration routine. Basically a script that parses the old 0.4 database, converts the values to be compatible with the new 1.3 database and populates it.

but if i need 0.4 (8.6 tibia) to 1.3 (8.6 tibia), i want to use this same exemple?
 
but if i need 0.4 (8.6 tibia) to 1.3 (8.6 tibia), i want to use this same exemple?

Yep. Worst case scenario a backport of TFS 1.3 to client 8.6 might have some custom changes in the database, but same principle can be followed.
 
Back
Top