Discussion of general topics related to the new version and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
Forum rules
Discussion of general topics related to the new release and its place in the world. Don't discuss new features, report bugs, ask for support, et cetera. Don't use this to spam for other boards or attack those boards!
oldlock wrote:
I am assuming that the converter will work on a snapshot of the database as it was at the moment of conversion & that any changes made to the original database after the conversion will have no effect ...
Question: given that the conversion takes minutes to hours, is the original board avaiable in the meantime? In this case, isn't there the risk of inconsistencies in the new DB?
Also, new data/posts/etc added/modified/removed during/after conversion are not included in the new DB.
In other words: is there (or will there be) an option to put the old board unavaiable when starting convertion, or will this have to be done manually?
Not sure whether it's in the documentation, but I know I read somewhere to manually make the old board unavailable prior to commencing the conversion.
oldlock wrote:
Not sure whether it's in the documentation, but I know I read somewhere to manually make the old board unavailable prior to commencing the conversion.
Documentation + average user = uh?
Would be definitely better to have this as an option in the updater.
Or, at least, a very big red bordered blinking advice telling to do it manually, and to proceed you have to click three times 'Yes' to the questions "Did you do it?" "Are you sure you did?" "Are you really really sure you did?"
I finally found how to solve my "MySQL server has gone away [2006]". One post had a huge amount of text "". I didn't look for the fault in the convertion tool but here is the SQL of that post.
". I didn't look for the fault in the convertion tool but here is the SQL of that post.