Hi Ariel, > Before sending an email concerning some problem, I always try to search > the issues database (nobody likes to read twice the same thing),
I like this attitude :) > and I > found this issue 74732 (summary says that cannot access any HSQLDB data > when *connection pooling is enabled* ) > > but I thought that it was a different one, because I *never* enable the > connection pool (for all the comments I've heard, it seems to cause too > many problems). Depending on the database/driver type, different components inside OOo are used to provide the same functionality (simplified: this depends on how much functionality can be provided by the DB's driver, and how much must be built by Base on top of this). The bug which caused issue 74732 manifests in a variety of ways, depending on which of those components is internally used. For embedded HSQLDB, it's needed to enable connection pooling to trigger the bug. For other database types, it's not needed, since they're accessing using other code, where the bug fires in another position. >>I'd urge you to submit an issue for this > It's issue nr. 76555 Thanks, I marked it as duplicate ;) > I downloaded the dll for Win, but in $insturl/OOo2.2/program/ there is > already dbtools680mi.dll, should I replace it? Yes (after doing a backup, of course) > By the way, when I find that there is an issue open, what is more > efficient, duplicating the issue or voting for it? > Frank's words seem to suggest the first one: > >>I'd urge you to submit an issue for this, even if I can tell you already >>that I will mark it as duplicate of issue 74732. The reason is that the >>more different duplicates we get, the higher are the chances I'm allowed >>to fix this for 2.2.1 (hurdles for 2.2.1 are pretty high, and so far I >>don't have the approval, yet). In this case, it's simply that 74732 had already been fixed for the 2.3 branch. But I wanted to have it for 2.2.1, and since the hurdles for 2.2.1 are very high, I needed good arguments. Being able to point to a lot of people which have the same problem with different databases *is* a good argument. I would not have asked you to submit an issue if the problem had been known for Derby before. That is, we knew it happened for embedded HSQL with pooling, for PostgreSQL JDBC, and for some other types, but not (so far) for Derby. Thus, I thought it's a good idea to document that there's yet another DB affected. With this, please consider this a special situation. As much as I like resolving issues as duplicates (since it decreaes the number of open issues), Andrew is right that *intentially* submitting dups is a bad idea since it causes unnecessary work only. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
