Deleting versioned class
 
CapableObjects Forums
Home       Members    Calendar    Who's On
Welcome Guest ( Login | Register )
        


««12

Deleting versioned class Expand / Collapse
Author
Message
Posted 2010-05-06 22:03:30
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2010-05-18 21:46:50
Posts: 85, Visits: 398
Hi Peter,

did you find any error/problem in here?

thanks,
Johannes
Post #5190
Posted 2010-05-13 13:30:39
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: Yesterday @ 16:39:39
Posts: 47, Visits: 200
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.

Post #5214
Posted 2010-05-15 01:17:03
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: Yesterday @ 16:39:39
Posts: 47, Visits: 200
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.

Post #5216
Posted 2010-05-16 14:33:41
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2010-05-18 21:46:50
Posts: 85, Visits: 398
Reported to mantis: #905

And I will go on to figure out where the problem is coming from...
Post #5220
Posted 2010-05-16 15:22:34
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2010-05-18 21:46:50
Posts: 85, Visits: 398
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
Post #5221
Posted 2010-05-18 20:11:55
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: 2010-09-03 10:28:49
Posts: 173, Visits: 2 010
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 )

Post #5226
Posted 2010-05-18 20:35:00
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2010-05-18 21:46:50
Posts: 85, Visits: 398
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
Post #5227
Posted 2010-05-18 20:56:59
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 2010-05-18 21:46:50
Posts: 85, Visits: 398
Hi,

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

Thanks,
Johannes
Post #5228
Posted 2010-05-25 11:39:56
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: 2010-08-23 23:54:43
Posts: 1 228, Visits: 1 374
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


/Jonas Hogstrom [CapableObjects]
Post #5245
« Prev Topic | Next Topic »

««12

Reading This Topic Expand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: HansKarlsen, Jonas Hogstrom

Permissions Expand / Collapse

All times are GMT +1:00, Time now is 10:32

Powered By InstantForum.NET v4.1.4 © 2010
Execution: 0,344. 11 queries. Compression Disabled.