CapableObjects Forums / ECO / General discussions / Deleting versioned class / Latest Posts

RE: Deleting versioned class

Jonas Hogstrom — Tue, 25 May 2010 11:39:56 GMT

I have identified the problem that causes this. It was a case of code tidying that went wrong. There was a property that kept track of the relevant timestamp that used to be backed by an explicit field. The property was now backed by a compiler generated field, but the original field was still left in the code and was set by some code (instead of setting the property with the compilergenerated field).

The fix for this will be checked into the ECO 5 branch today and should be in a build on http://dl.capableobjects.com/dailybuilds/ later tonight.

/Jonas

RE: Deleting versioned class

Johannes Klos — Tue, 18 May 2010 20:56:59 GMT

Hi,

Edit:
updated to Eco6, still have the same error.....

Thanks,
Johannes

RE: Deleting versioned class

Johannes Klos — Tue, 18 May 2010 20:35:00 GMT

Hi,

I haven't tried Eco6, since I do not have a licence for it. I will download the test version and see what it is doing.

Johannes

RE: Deleting versioned class

HansKarlsen — Tue, 18 May 2010 20:11:55 GMT

I took your project from mantis, and added Product, set some values on the amounts, saved, restarted server and client...

It all seems to churn along ok... I cannot repeat this (using current build eco6 )

RE: Deleting versioned class

Johannes Klos — Sun, 16 May 2010 15:22:34 GMT

Hi Peter,

in order to figure out wether the persistance server is the cause i created a Eco project without a persistance server, so i have the sql connection stuff in the mein program. It still does NOT work. So it is not the persistance server...

Bye,
Johannes

RE: Deleting versioned class

Johannes Klos — Sun, 16 May 2010 14:33:41 GMT

Reported to mantis: #905

And I will go on to figure out where the problem is coming from...

RE: Deleting versioned class

Peter Buchmann — Sat, 15 May 2010 01:17:03 GMT

Hi Johannes,

I've tried to create a application from scratch like you did with the same functionality:

* WinForms application with persistence server
* One class with versioning
* WinForms only has Eco debugger on it where I was able to add and delete versioned objects.

The result was: The application that was automatically created from the Eco project template did NOT work with versioning. I've tried with Eco version 5.0.0.4754. Something has to be missing in the template for versioning.

RE: Deleting versioned class

Peter Buchmann — Thu, 13 May 2010 13:30:39 GMT

Hi Johannes,

sorry that I didn't answer earlier.

I think I know what your problem is but still don't know how to solve it as we are still in ECO3 and don't work with a persistence server.

You persistence server doesn't know something about your EcoPackage. Just try to rename a table in your model (change attribute tablename in model). Your Ecospace knows the correct table name, your persistence server doesn't. So the additional infos in the ecopkg file are not known to the server an so it thinks that the table item is not versioned (as this info is also contained in the file).

I still don't know how to tell this Info to the server. Maybe someone else does.

RE: Deleting versioned class

Johannes Klos — Thu, 06 May 2010 22:03:30 GMT

Hi Peter,

did you find any error/problem in here?

thanks,
Johannes

RE: Deleting versioned class

Johannes Klos — Sat, 01 May 2010 14:21:20 GMT

Hi Peter,

I have created a small project which shows two errors (Assertion error, different thread and the deleting objects problem) It is attached to the thread here. In here I have an Order...Item association (1..n) and I cannot delete items. After restarting the app they appear again. I think the TIMESTAMPSTOP values are all set correctly (from MAXINT to the corresponding TIMESTAMPSTART-value in the items table). The SQL which is created for Items.Allinstances (would correspond to Rezeptur.allinstances) looks the following:
[code]SELECT ECOModelRoot_A.ECO_ID, ECOModelRoot_A.ECO_TYPE FROM ECOModelRoot ECOModelRoot_A INNER JOIN Item Item_A ON ECOModelRoot_A.ECO_ID = Item_A.ECO_ID AND ECOModelRoot_A.TIMESTAMPSTART = Item_A.TIMESTAMPSTART [/code]

The expressionhandle returns all objects (incl the deleted ones) and looking at the SQL I see that there is no comparison with TIMESTAMPSTOP. It will get the latest result, also when its TIMESTAMPSTOP value is set.

If I have an error in the project, I do not know at the moment where it is :)

I also have inheritance in the main-project, not in the attached testproject.

Thanks,
Johannes

RE: Deleting versioned class

Peter Buchmann — Sat, 01 May 2010 00:20:40 GMT

Johannes,

first of all, we are using versioning with ECO3 and there are a lot people that are also using versioning. Deleting objects works for us and so I think that there is no basic problem within ECO.

So we have to find out, what's going wrong for you. I am wondering about following:

1) Versioning usually needs a TIMESTAMPSTART column in the table which corresponds with the value of the column TIMESTAMPSTART in table ECOMODELROOT.
2) The created SQL needs a join with ECOMODELROOT to get the current objects. Join columns have to be ECOID and TIMESTAMPSTART, in the where clause TIMESTAMPSTOP is compared to MAXINT. Please try following: Find out which SQL is generated for your OCL statement "CL_Rezeptur.AllInstances" and post this SQL here. Your SQL is loading a specific object. While doing AllInstances you should only get the IDs of the objects.
3) There must be a wrong setting somewhere in your configuration but with your current error description I cannot imagine where the error is. Have you switched on versioning in Modlr for this specific class (value of attribute "versioned" must be set to true)?
4) Have you got inheritance in you model?

RE: Deleting versioned class

Johannes Klos — Fri, 30 Apr 2010 16:39:13 GMT

Hi,

I created a testproject which shows the same error.

Running expressionhandle versus OCLPSHandle results in different results:
expresisonhandle returns the amount of objects (incl the deleted ones) so for example 3 (2 "excisting" and 1 deleted)
OCLPS returns for example 5 (incl. older "versioned" objects..)

What can I do? This way, it is hard to use Eco with versioning...

Thanks,
Johannes

RE: Deleting versioned class

Johannes Klos — Fri, 30 Apr 2010 08:55:16 GMT

Hi Peter,

I am using an expression handle, which I assume is using OCL and not OCLPS???

The OCL-Query is self.produktionsDaten.Rezeptur which returns a list of Rezeptur.

Maybe we should reopen a new Mantis for it?

Thanks, (Dankeschön!!)
Johannes

RE: Deleting versioned class

Peter Buchmann — Fri, 30 Apr 2010 01:21:34 GMT

Hi Johannes,

are you using OCL or OCLPS for querying the data? Please recognize that only OCL ist working correctly for versioned classes.
You cannot use OCLPS for versioned classes as it shows such errors.

And now in our boths mother language:

Ich habe dazu vor Jahren einen Mantis-Fehler (#480) eröffnet, der immer noch nicht gelöst wurde. (I opened a mantis bug #480 years ago for this issue which is not solved for now).

RE: Deleting versioned class

Johannes Klos — Thu, 29 Apr 2010 14:52:15 GMT

Hi Peter,

I had a close look and it looks like a wrong SQL-phrase.

The TIMESTAMPSTOP ist set to 2147483647 (MAXINT) before deleting, and 14 (or a different value, depending on the state of th DB of course) after deleting the object and the class is set to versioned in the model (I switched UseClockLog,UseTimestampColoumn and usetimestamptable to true in the p-mapper)

I had SQL profiler running while loading the data and the sql which is used to get the list is this one:

[code]exec sp_executesql N'
SELECT Rezeptur_A.ECO_ID, Rezeptur_A.ECO_TYPE, Rezeptur_A.ProduktionsDaten, Rezeptur_A.LastModifiedTime, Rezeptur_A.CreatedTime, Rezeptur_A.CreatedBy, Rezeptur_A.LastModifiedBy, Rezeptur_A.Edukt, Rezeptur_A.EduktName

FROM Rezeptur Rezeptur_A

WHERE Rezeptur_A.ProduktionsDaten = @ID0',N'@ID0 uniqueidentifier',@ID0='B8BA38E3-51F3-4E94-A197-5E835EFF43F3'
[/code]

The ID0 is the correct ID for the single object which has multiple Rezeptur classes (sorry that the data is in german)

It seems that ECO is not adding the TIMESTAMPSTOP<>MAXINT to the SQL-query. How can I do this?

Thanks,
Johannes

RE: Deleting versioned class

Peter Buchmann — Wed, 28 Apr 2010 01:16:48 GMT

This could have several reasons (we are using versioning since years and never had problems, so what I'm now wrinting is hypothetical):

* Is TIMESTAMPSTOP set to a value less than MAXINT? I would assume this now.
* The class must be set to be versioned in the model.
* ECO shouldn't see your deleted objects as it creates SQLs that only show objects that have a TIMESTAMPSTOP with value MAXINT in table ECOMODELROOT. So please check the generated SQL (maybe with debugger).
* Please post this SQL. I think we can find the error when we have the SQL.

RE: Deleting versioned class

Johannes Klos — Tue, 27 Apr 2010 13:24:36 GMT

Hi,

the TIMESTAMPSTOP is set, but the dataset is not deleted, which I suppose should not be deleted anyhow.

What is wrong?

Thanks,
Johannes

RE: Deleting versioned class

Peter Buchmann — Mon, 26 Apr 2010 21:28:45 GMT

Hi Johannes,

deleting a versioned object is done by setting the value TIMESTAPTSTOP in table ECOMODELROOT.
Please check if this value is set for the deleted object (seach for ECOID).
Maybe check which SQL is generated by deleting the object.

Deleting versioned class

Johannes Klos — Mon, 26 Apr 2010 19:30:34 GMT

Hi,

I have a 1..n association between two classes, both are versioned. I want to remove one item from the list and delete it. I do the following:
item.AsIObject().Delete();

The object dissappears in the list and I save the ecospace. After restaring the program, it is in the list again.

Am I doing something wrong?

Thank you,
Johannes