On Mon, Feb 16, 2004 at 07:46:49PM -0600, Jay Hannah wrote: > I shouldn't need the warning, especially when it's > wrong. Even so, it has been useful to me on many occasions in > dialogues like this:
Well, as I have thought about it more, I agree that there is some tension between the system warning you when you're "sloppy", and the system doing things automatically (ie, garbage collection). You could argue that database handles are more precious than most resources, like memory and filehandles, so you should be extra careful with them. On the other hand, that is reminiscent of the C mentality that you have to keep track of every resource by hand. I come down on the side of "let the system handle it", but I can see why you'd be concerned. The warning was a sort of poor-man's dbh leak detector. > > Incidentally, you already don't get the warning during global > > destruction, so it isn't that reliable. > > I ran a little test against all our productions RDBMSs. As luck would > have it, it seems that it is being thrown in global destruction in the > 2 DBD's I use the most. I didn't realize until now that it's not being > thrown in the others. As Tim suggested, I bet that what you're seeing is dependent on some feature of the programs (and how they interact with the garbage collector), not the DBDs. Andrew
