On Sat, 27 Oct 2001 04:07, John McNally wrote: > I read the statement below to say it would fail in the case that you are > using one database that is not named (other than "default"). I know > this not to be the case. And as far as I can tell whether there is one > db or many and whether they are named or not in the xml file, dbName in > Criteria will never be null. It is set to the default in the > constructor and the setter converts null to the default.
right. > In the case that you name your db's in the xml file. The Peer will make > sure the criteria is set to the proper name. setting the name to any > value will have no effect because the peer will override it. Thats not the behaviour I was seeing. The code was not setting the db name and thus the criteria was searching against the default database when the peer wass associated with another database. > I am not using multiple db's, but others are and they pointed out a few > bugs/features early on that have been fixed/added. You are obviously > talented enough to add any functionality you find lacking, why not work > on it? And please explain to me what errors you are getting, I can't > see the problem in the code. I will look into it. I won't be at that site till thursday next but from what I recall the BlahPeer.doSelect() was not setting the database to the database that Blah is associated with. I will send a patch to fix this when I get in there again. -- Cheers, Pete ----------------------------------------------------- First, we shape our tools, thereafter, they shape us. ----------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
