> it is all so easy with other dbs, but with postgresql > it is a nightmare... the only solution I can see is to remove the > declarative transactions in Spring and start using manual transactions > blocks around everything that could possibly go wrong... just because of > a quirk in postgresql.... This may or may not be a design flaw in postgresql, but perhaps you could reduce the emotional pitch of your emails - some people here (and I am not one of them, to be honest) put a lot of work for no payoff except the pride of contributing to a good product, and to have it insulted seems, well, personally insulting, not to mention unprofessional and a little silly and not something that belongs on a listserv. That being said, I feel your pain. Perhaps we can take this as an opportunity to make the product better, rather than an opportunity to bag on it by calling it "quirky" and "a nightmare". > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
