|
|
|
[
Permlink
| « Hide
]
Vidisha Sharma - 11/Jul/07 10:06 AM
Testcase attached
The problem was a circular "tree" created through candidate filtering. Fixed for this specific case, but IMO the Tree API/design should be changed to avoid scenarios like this - see COR-727.
Hi Patrick,
When will the db4o v6.1 be availaibe with this fix? Regards, Vidisha Hi Parrick,
This issue seems to be still there for the following query IQuery query = db.Query(); IConstraint a = query.Constrain(typeof(A)); IConstraint b = query.Descend("Arry").Descend("B_Name").Constrain("BName"); IConstraint c = query.Descend("Arry").Descend("C_Name").Constrain("CName"); a.And(b); a.And(c); IConstraint b1 = query.Descend("Arry1").Descend("B_Name").Constrain("BNamex"); IConstraint c1 = query.Descend("Arry1").Descend("C_Name").Constrain("CNamey"); a.And(c1); a.And(b1); IObjectSet result = query.Execute(); Hi Patrick,
my class hierarchy is little complex. My problem is if I write constraints in one sequence the query works appropriately. If the change the sequence of constraints the querys stops working. I am attaching a testcase along which demonstrates this kind of behaviour. Regards Vidisha I am reopening this issue as I have encountered one more isse which I am uploading as testcase.
check the attached file 'ComplexTestCase.zip' which demonstrates this testcase.
The reopened case looks like a completely different issue to me. Re-checked in as COR-768.
Hi Patrick,
Now this issue is reproducible at your end. This is a very critical issue and causing lots of problem to us. Can this be taken on priority. Regards, Vidisha Fixed, ported back to 6.3 and 6.1 branches.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||