This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have tried both mysql5 and multiple sqlserver data providers and multiple variations of the connection strings (validating them in other apps) and every time i right-click Update Database or Update from Source, VS2012 thinks a few seconds and then nothing (no Update Database dialog). I don't see anything in Event Viewer, no dialogs, nothing. For the record, my environment:
|
|
|
Turns out this is not related to my installation/environment, but the model itself. When I create a very simple model (single entity) the round-tripping works fine. But with my actual model both Update Source and Update From Database fail silently. The solution builds, there are no warning or errors. I will start building the model again from scratch and doing an update with every entity added, but what is the best way to troubleshoot this issue? |
|
|
That's interesting - I have just come here to post about the same issue! I have just tried the latest version of LS but I have the same issue, it just silently fails when updating the DB. I'll post back if I find any details... |
|
|
I may have found the issue, I managed to get my model created on the DB by manually updating single tables and links at a time, this gave some feedback on errors where it could not add referenced tables etc. Using this I just updated tables and link bit by bit and this worked. I then created a simple test model with three tables, each linked to the next...
Trying to update the DB with the above silently fails. I think if you kept updating your model to the DB as you were creating you might never see this issue as in the above test you can do the following... Create this first... (ie Table3 is not linked to Table1)
Send that to the DB and then create the link from Table3 to Table1 and it will work. |
|
|
This is ultimately what I ended up doing. Instead of going all out with dozens of linked tables before the first update, I would update early and update often and the issue went away. Regardless, silently failing is not helpful. |
|
|
Hi all, The issue here is that you have a circular reference in the graph when performing the update. This is not supported although you can work around this as you have found by performing the updates in stages. Ive added in an update to properly report this as an error which will be pushed out in the nightly builds shortly, the lack of feedback is certainly an issue. Be aware though that circular references are not supported at runtime as we need to be able to determine the insertion/update ordering so if you have an update which spans the circular reference you have defined this will trigger a runtime exception.
|
|