Hello, I'm getting an exception during schema upgrade with DO 4.3 (Release version) after update from previous version. The domain build mode is "Perform".
To be precise I'm not seeing it in debugger only (it is not caught by your code) Do you need additional information? Besides the assemblies from the installer do not have the same file version : is this normal? Regards, Updated at 15.07.2010 9:43:07It would be difficult not to give you our complete application, and I would like to avoid this if possible. An information I can add is that I've looked at the "action" parameter of method Xtensive.Storage.Providers.Sql.SqlActionTranslator.ProcessUpdateDataAction(DataAction action) It show like this in debugger: {Update 'Tables/SPB.Tools.FileManipulation.ImportFile' set () where ()} Xtensive.Modelling.Actions.DataAction Property "Difference" shows {"./Tables/SPB.Tools.FileManipulation.ImportFile" != "./Tables/SPB.Tools.FileManipulation.ImportFile" (NodeDifference): Unknown DataChanged} Xtensive.Modelling.Comparison.Difference {Xtensive.Modelling.Comparison.NodeDifference} I'm sorry to report this issue with so little debug information, nevertheless it's a big issue for us. I'm pasting below screenshots from visual studio : tell me if it helps, or if you need more specific information I would be able to find with debugger. [attachment=1:3hx3p33v]do1.png[/attachment:3hx3p33v] [attachment=0:3hx3p33v]do2.png[/attachment:3hx3p33v] Updated at 16.07.2010 9:27:41I can confirm the problem is still there with latest 4.3 release. I will try to understand the problem, with newly provided pdbs. Updated at 19.07.2010 8:08:48Hello, I managed to reproduce it with a sample project: http://olorin.dinauz.org/temp/TestDoUpgradeBug.zip Steps to reproduce: * Build the project with DO 4.3 RC4 * Launch in Recreate mode * Build the project with 4.3 release In short for you : You can use the .bak file to get the DB at the state after recreate on RC version. Then launch the project in .zip, and should the exception. Updated at 21.07.2010 12:54:57Any news on this problem? It still occurs with build 5605 Updated at 21.07.2010 14:26:43Please sleep, that's not that important! ;) This thread was imported from our support forum. The original discussion may contain more detailed answer. |
mahdness wrote:You should be writing that NHibernate comparison, not fixing bugs (or even worse, sleeping!!!) :wink: Of course I'm joking (maybe :wink:)... but anyway once you get that published I'm sure many customers are going to comment about the amazing support as being a huge asset for DO. xumix wrote:Just got the same @ latest 4.3.1
Db backup + .dll are attached Alex (Xtensive) wrote:The bug is fixed. The issue occurs, if type T having a reference property R is removing, but there is EntitySet<t> paired to R. E.g. it was impossible to upgrade from:
To:
Workaround for now is to manually remove the table mapped to type T (i.e. for type Address in this case) before upgrade. Forgot to add: it was issue 772. |
Domain build code + database backup (at least, schema) would help the best.
It seems this is really a bug.
"Domain build code" = actually, something we can launch to reproduce this, e.g. even your own .exe is enough.
You can send us .exe + database backup allowing to reproduce the problem here.
I downloaded the test - you can remove it.
I will be trying to fix it today (till the morning ;) ).
I can't sleep while some customers aren't satisfied. The only way to make me sleep is to stop posting bug reports here ;)