BTW: that's not a postgres problem, ANY relational database will give the same error here.
I didn't suspect it to be a postgres problem. I only didn't have the opportunity to make this mistake working with MySQL. :-)
best, Christoph
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx
