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.

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

What is wrong?

Thanks,
Johannes

* 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.

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:

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'

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

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).

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

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?

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