ODBC Errors

[Thomas Mercer-Hursh]

In working to sort out a programmatically created model (see thread on Integrity Check), I am getting a couple of ODBC errors.  The first of these comes just on opening a couple of the higher level packages:

Microsoft OLE DB Provider for ODBC Drivers [-2147217873]
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEGE]Integrity constraint violation:uniqueness constraint violation(7518)

Any log someplace that might tell me what it is actually complaining about, i.e., which table or which constraint?

The other one is a little more helpful:

Microsoft OLE DB Provider for ODBC Drivers [-2147467259]
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEGE]Column VALUE in table PUB.T_OBJECTPROPERTIES has value exceeding its max length or precision.

OK, so I know the issue is T_OBJECTPROPERTIES.VALUE, but what is the constraint on max length that I am violating?

[«Midnight»]

255

[Thomas Mercer-Hursh]

I don't suppose there is any way to up that .... seems quite limiting.

[«Midnight»]

It's worth asking; they've done it in past.

Also, check the various schema for DBMS repositories. I used the Access model.

There might be a way of using the Notes field, which is a BLOB, to contain longer values. Sort of like what happens with Tagged Values of Memo type.

David

[Thomas Mercer-Hursh]

Well, one of the interesting things about an undocumented schema is that in the schema I am looking at both Value and Notes are both Character with a maximum length of close to 32K.  I see in Access though, that one is Text and the other Memo.

So, I could put the long ones in Notes ... but I don't see where in the UI that one would be able to see them.  Notes aren't very useful if one can't see them!

[KP]

So, I could put the long ones in Notes ... but I don't see where in the UI that one would be able to see them.  Notes aren't very useful if one can't see them!

Put your text in Notes and set Value=<memo>. It will act as a memo-type tagged value.

EDIT: This gets around the size limitation for the following fields only: t_objectproperties.Value, t_attributetag.Value, t_operationtag.Value, and t_connectortag.Value.

[«Midnight»]

You will have to do some homework on this. That's why I mentioned tagged values. Normally they Text (as in data type) field is used, which cuts them off at 255. But if the tagged value is designated as being a Memo (as in EA terminology) the Notes field seems to be used, which is a BLOB (also type "memo" in Access, so I avoided that word in this context).

I do not know if there is some way to make the same distinction (type of value) for object properties. If there is some analogous mechanism you are likely in business. If not you should (IMO) make a feature request to Sparx.

My gut feeling is that something along these lines is possible. After all, in the 'new' data modeling paradigm stored procedures are stored individually, and the properties table seems to be where the content of the SP is kept. Surely stored procedures can have code longer than 255 characters...

David

[Thomas Mercer-Hursh]

Anyone going to chime in on the other error, where I don't know which table it is unhappy about?