MySQL Bugs: #20620: file open gives lua call error (not a GRT object)

Bug #20620	file open gives lua call error (not a GRT object)
Submitted:	22 Jun 2006 6:58	Modified:	3 Aug 2006 10:51
Reporter:	Ajna Cackovic	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S1 (Critical)
Version:	1.0.6beta	OS:	Windows (win xp pro sp2)
Assigned to:	Sveta Smirnova	CPU Architecture:	Any

Description:
while trying to open a .mwb (from the file menu) created with 1.0.6beta within the same version, the following error is generated:

Workbench.loadDocumentData :Error calling lua function Workbench.loadDocumentData: ./lua\Workbench.lua:502: Value assigned to a GRT reference member is not a GRT object (dict with _id member) Error Nr.10008

i have found no way to open this file i created as of yet. other (simpler) files that i have saved open ok, however.

How to repeat:
i can repeat this error with my one file. this file causes the error on other computers running 1.0.6beta

I can open your file without any error and see all tables in the Object Tree, but nothing in Layers and nothing in Main View.
Which error causes attached file on other computers?

are you asking what error i get on other computers? if so, i get the same error on another windows xp pro sp2 box. also i should rephrase 'error' as 'message'.

all the tables (about 45) you see were laid out (and linked) in the workspace. i don't know anything about the xml schema you use for workbench, but if i understand what i'm reading, then the layers are present on the workspace in the mwb file.

the layers were created with the reverse engineering function (auto arrange, i've had render errors with grid placement) and then positioned/arranged by hand

Could you please provide us database structure only dump of the database which you reverse engineered? (mysqldump --no-data)

you bet. the file is posted now (private). this is slightly different than the version that was used in workbench (some field data restrictions, comments, and a few fields were added, no new tables though)

Problem happens when in .mwb file there are string likes:
<value type="string" key="table" option="ref">{9133A21B-1D57-46EC-A858-B2DD896FA172}</value>

where "{9133A21B-1D57-46EC-A858-B2DD896FA172}" is unique value for whole document.

I think it can happens when one element has been removed, but reference to it not. But I can not repeat it yet.

When I arrange objects using "Arrange elements" feature on copy of your dump, save and close model in 1.0.6, all relationships between objects expire and not restore nor after document reopen, nor after application restart. But in 1.1.1 all work fine (if not take in account bug #19064). In 1.0.6 is only repeatable with database restored from your dump and not using simple files. But I can not make other distruction of the file as you describe.

Because in MySQL Workbench 1.1.1 I can not repeat problem with element arranging, I change status of the bug to "Can't repeat". But if you can any idea how to repeat damage don't hesistate to reopen the bug.

You can download MySQL Workbench 1.1.1 here: http://dev.mysql.com/downloads/gui-tools/5.0.html

I have the exact same error message. I use version 1.1.8 alpha. When I try to open a file the same message that Ajna reported appears, and the file doesn't open