antville/helma
antville/helma
1
1
Fork 0
Code Issues 5 Pull requests 5 Projects Releases 5 Activity Actions

Pass application object in constructor for internal DbMapping

Browse source 
object.

In checkConstraints(), if a filter property is set, never return
true if the object has been modified since it was fetched from
the database. This is the only way we can be sure that the
constraints are fulfilled without evaluating the filter expression.
This commit is contained in:
hns 2001-12-06 22:40:30 +00:00
parent 9da4b1dec9
commit 24b8f34382
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
src/helma/objectmodel/db/Relation.java
View file

@ -360,7 +360,7 @@ public class Relation {
if (!virtual)
return null;
if (virtualMapping == null) {
virtualMapping = new DbMapping ();
virtualMapping = new DbMapping (ownType.app);
virtualMapping.subnodesRel = getVirtualSubnodeRelation ();
virtualMapping.propertiesRel = getVirtualPropertyRelation ();
}
@ -483,6 +483,14 @@ public class Relation {
* Check if the child node fullfills the constraints defined by this relation.
*/
public boolean checkConstraints (Node parent, Node child) {
// problem: if a filter property is defined for this relation,
// i.e. a piece of static SQL-where clause, we'd have to evaluate it
// in order to check the constraints. Because of this, if a filter
// is defined, we return false as soon as the modified-time is greater
// than the create-time of the child, i.e. if the child node has been
// modified since it was first fetched from the db.
if (filter != null && child.lastModified() > child.created())
return false;
for (int i=0; i<constraints.length; i++) {
String propname = constraints[i].foreignProperty ();
if (propname != null) {