topic Re: Persistent class for a database view; cannot activate in Application Development and Automation Discussions

Persistent class for a database view; cannot activate

Former Member — Mon, 24 Aug 2009 12:27:23 GMT

I've created a database view which represents data from multiple ECC tables, joined on several fields.

Now I want to access the data available from that view through a persistent class.

I have mapped all fields as readonly, but it doesn't work. The error I'm getting when I check the mapping is:

"Database operations with view ZMYVIEW are not allowed".

Any ideas?

Edited by: René van Mil on Aug 24, 2009 2:27 PM

Re: Persistent class for a database view; cannot activate

Former Member — Thu, 27 Aug 2009 12:51:08 GMT

Hello René,

I have an assumption:

The persistency framework provides functionality to create, read, update and delete objects (through the agent class). If you have marked all the properties of this object as "read only", this is only relevant when you work with existing object (so they are protected against updates). But the framwork will also create code which inserts or deletes complete records. If the view is read-only (which it is if you used several tables with a join), this cannot work.

Regards

David

Re: Persistent class for a database view; cannot activate

Former Member — Thu, 27 Aug 2009 13:07:24 GMT

David, I was thinking the same, it probably just doesn't work with tables joined in a view. Though I was hoping I might have done something wrong creating the persistent class.

So I guess I'll have to write the class to access the view myself.