No error, but qualifier is still inserted. I've had no time yet to insvestigate. I'm doing this:
ObjEntity clone = (ObjEntity) SerializationUtils.clone(objEntity); clone.setDeclaredQualifier(null); SelectQuery query = new SelectQuery(clone); ... BTW this thing will only work on the trunk, because Cay entities are made serializable in CAY-1080 and not in M4. I have qualifiers in all tables (deleted="0", as I've already explained somewhere). But sometimes I will need all records, even deleted ones. 2008/11/11, Andrus Adamchik <[EMAIL PROTECTED]>: > > I am not a big fan of entity qualifiers for things other than inheritance, > as sooner or later you'd end up trying to work around it to get data they > are hiding. And there's no way to just turn them off... Anyways, entity > cloning hack should work, but may require some tweaking. So what exactly is > the error? > > Andrus > > > On Nov 11, 2008, at 2:00 PM, Andrey Razumovsky wrote: > > Wow, I ran into same question yesterday (if you mean ObjEntity qualifiers). >> Still have no answer though. I though I could perform a SelectQuery with a >> phantom ObjEntity which is created by cloning ObjEntity with qualifier and >> setting qualifier to null, but that doesn't seem to work. >> >> 2008/11/11, Lachlan Deck <[EMAIL PROTECTED]>: >> >>> >>> Hi there, >>> >>> I'm just wondering if it's possible to get a DataContext that has the >>> restricting qualifiers (as defined in the model) turned off? >>> Thanks. >>> >>> with regards, >>> -- >>> >>> Lachlan Deck >>> >>> >>> >>> >>> >
