Re: derbytools/dblook_test fails

Hi Myrna & thanks for your answer. Myrna van Lunteren wrote (2005-05-08 17:12:58): > Hi Bernt, > > Yes, derbyall suite should pass... > > Whenever there's a test failure in the full suite, step 1 is to run > the test by itself. > Does that fail too? Yes. I've done that. > > I syn

Re: [jira] Commented: (DERBY-104) Get rid of the Max lenght of 18 for constraint names

Thanks for you answer, Daniel John Debrunner wrote (2005-05-06 06:47:41): > Bernt M. Johnsen (JIRA) wrote: > > [ > > http://issues.apache.org/jira/browse/DERBY-104?page=comments#action_64618 ] > > > > Bernt M. Johnsen commented on DERBY-104: > > --

BulkInsert ? (Re: DERBY-167 has done but ...)

Hello. (B (BSatheesh Bandaram wrote: (B>Import code actually uses bulkInsert option, so it would be good to test (B>this code path too. I can help, if needed, on these tests. Before commiting (B>the patch, it would be good to add more tests (B (BCan I execute bulkInsert using next method ?

Re: derbytools/dblook_test fails

Hi, BMJ> > > *** Start: dblook_test jdk1.4.2_02 derbyall:derbytools 2005-05-06 22:37:37 *** BMJ> > > 4861d4860 BMJ> > > < java.io.FileNotFoundException: BMJ> > > Test Failed. BMJ> > > *** End: dblook_test jdk1.4.2_02 derbyall:derbytools 2005-05-06 22:37:53 *** I had this same problem and de

[jira] Created: (DERBY-266) test tools/dblook_test.java fails if run in a directory having "*derby/*" in its path

test tools/dblook_test.java fails if run in a directory having "*derby/*" in its path - Key: DERBY-266 URL: http://issues.apache.org/jira/browse/DERBY-266 Project: Derby Type: Bug

[jira] Updated: (DERBY-266) test tools/dblook_test.java fails if run in a directory having "*derby/*" in its path

[ http://issues.apache.org/jira/browse/DERBY-266?page=all ] Dag H. Wanvik updated DERBY-266: Version: 10.1.0.0 Fix Version: 10.1.0.0 > test tools/dblook_test.java fails if run in a directory having "*derby/*" in > its path >

Re: derbytools/dblook_test fails

"Dag H. Wanvik" <[EMAIL PROTECTED]> writes: [snip] > so if your tests are running in a directory containing this pattern, a > line too much is deleted from dblook_test.tmp, thereby giving a > comparison failure like you describe. > > I don't know the reason for this deletion yet, so I can't say h

Unified DataSource API

There has been a fair amount of discussion recently about keeping compatibility between the embedded and client APIs for creating and configuring DataSources. We currently have three DataSource implementations: * EmbeddedDataSource - used by the SE embedded impl * EmbeddedSimpleDataSource - used

[PATCH] Derby 237 Boot errror stack traces from store must not be lost

http://issues.apache.org/jira/browse/DERBY-237?page=all This patch fixes derby-237: Boot errors from store must not lose error messages/stack traces in between. Actually nested exceptions from the boot error were not lost but their stack traces were not being written out into error stream which i

[jira] Assigned: (DERBY-236) Sane Mode and in our test environment, bootPassword gets written out in plain text to service.properties

[ http://issues.apache.org/jira/browse/DERBY-236?page=all ] Sunitha Kambhampati reassigned DERBY-236: - Assign To: Sunitha Kambhampati > Sane Mode and in our test environment, bootPassword gets written out in plain > text to service.properties >

TRUNCATE TABLE availability

Hi,   I was wondering on the latest status of TRUNCATE TABLE SQL: command. For the TODO list on the site I can tell that the code is basically complete but needs to be exposed – I was just wondering what are the details of the work items left and, if necessary, what I can help with to get

Re: Unified DataSource API

This sounds reasonable to me... Jeremy Boynes wrote: There has been a fair amount of discussion recently about keeping compatibility between the embedded and client APIs for creating and configuring DataSources. We currently have three DataSource implementations: * EmbeddedDataSource - used by t

Re: Unified DataSource API

Jeremy Boynes wrote: > There has been a fair amount of discussion recently about keeping > compatibility between the embedded and client APIs for creating and > configuring DataSources. > > We currently have three DataSource implementations: > * EmbeddedDataSource - used by the SE embedded impl >

I'm out travelling to the DB2 Technical Conference in EMEA

I will be out of the office starting 05/09/2005 and will not return until 05/16/2005. I'm currently travelling to Europe (Austria) and presenting at the DB2 Technical Conference. I'll reply to your note as soon as possible. Thanks, George

Re: BulkInsert ? (Re: DERBY-167 has done but ...)

(B (B (B (BBulkInsert is an internal mechanism, that gets used when you import (Bdata into a table, using Derby's import mechanism. (SYSCS_UTIL.SYSCS_IMPORT_TABLE) (BThis is not directly exposed to applications using JDBC or SQL, so (Bthere is no way to directly invoke it. If you write some

[doc] Suggestion for pasting links to the documentation

I have noticed a couple of emails lately referring to the documentation that is sourced in DITA. Specifically, they are references to individual topics within manuals using the output that creates many html files instead of one large one. However, it should be noted that simply grabbing the URL f

Re: BulkInsert ? (Re: DERBY-167 has done but ...)

Satheesh Bandaram wrote: (B (B> BulkInsert is an internal mechanism, that gets used when you import (B> data into a table, using Derby's import mechanism. (B> (SYSCS_UTIL.SYSCS_IMPORT_TABLE (B> ) This is not directly (B> exposed to applications usi

Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection

Hi, all. I have had some further thought on this, and I have a proposal. It seems like how one generates ids depends upon the environment Derby is running in. In a single-VM environment, probably the hashCode() solution is best because it works even if there are multiple systems in the same

Re: ApacheCon in Germany

> "BM" == Brian McCallister <[EMAIL PROTECTED]> writes: BM> I know Dan Debrunner offered to hold a Derby Internals BOF, which I BM> hope to attend. Not sure who else will be there. BM> BM> In past years ApacheCon has been my favorite con by quite a bit -- BM> sessions and people are ver

XSDA messages

I am working on a document for the Reference Manual that will list all of the messages in Derby. I have separated them out by Class code, but the problem is I have descriptions for every class code but one. For example, the description for Class Code XSDB is: "RawStore - Data.Generic transaction

Re: TRUNCATE TABLE availability

Have you tried DROP TABLE followed by a CREATE TABLE? That should work pretty good and is a good TRUNCATE TABLE implementation! :-) Satheesh rahul merwah wrote: Hi,   I was wondering on the latest status of TRUNCATE TABLE SQL: command. For the TODO list on the site I can t

Re: [doc] Suggestion for pasting links to the documentation

Thanks for the tip. I will use it next time. I noticed the URL wasn't pointing to the required section, but I thought people can just search once there in the manual. But, this is better. :-) Satheesh Jeff Levitt wrote: >I have noticed a couple of emails lately referring to >the documentation th

Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection

David Van Couvering wrote: > Hi, all. I have had some further thought on this, and I have a > proposal. It seems like how one generates ids depends upon the > environment Derby is running in. In a single-VM environment, probably > the hashCode() solution is best because it works even if there a

Patch for Derby-263 ...

Simple patch to remove UNICODEESCAPE option in IJ. Satheesh Index: java/tools/org/apache/derby/impl/tools/ij/ij.jj === --- java/tools/org/apache/derby/impl/tools/ij/ij.jj (revision 168631) +++ java/tools/org/apache/derby/impl/too

[jira] Commented: (DERBY-17) Network Server Needs to generate CRRTKN on ACCRDB if client does not send it

[ http://issues.apache.org/jira/browse/DERBY-17?page=comments#action_64795 ] Kathey Marsden commented on DERBY-17: - See the specifications at: http://www.opengroup.org/dbiop/ In particular, section 11.3.1 of: http://www.opengroup.org/onlinepubs/9699

[jira] Updated: (DERBY-246) XA end() fails with Connection is closed error

[ http://issues.apache.org/jira/browse/DERBY-246?page=all ] Myrna van Lunteren updated DERBY-246: - Description: I am testing ClientXADataSource. It fails when end() is called - here is the output fromn my test program. Running test org.simplejta.xat

Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection

David Van Couvering wrote: > Thanks for the quick reply, Dan, some responses below. > > Daniel John Debrunner wrote: > >> I'd like to see some crisper definition around what the return from >> toString() is meant to represent for a connection. >> >> - with this implementation, two different app