Why is that a good idea? In a complex application it'd be awfully easy to break logic that depends on such a thing.
True, but I think it offers a usefully concise syntax for simpler applications. Perhaps the documentation should be amended to mention the potential risks? (e.g. additional nextval() calls in between the nextval() you are interested in and the lastval()).
-Neil
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
