> -----Original Message----- > From: Radek Terber [mailto:[EMAIL PROTECTED] > Sent: Monday, September 18, 2006 11:21 AM > To: Derby Discussion > Subject: Re: Insert large using SQL > > Michael Segel wrote: > >> -----Original Message----- > >> From: Radek Terber [mailto:[EMAIL PROTECTED] > >> Sent: Monday, September 18, 2006 10:56 AM > >> To: Derby Discussion > >> Subject: Re: Insert large using SQL > >> > >> Michael Segel wrote: > >> > >>>> -----Original Message----- > >>>> From: Radek Terber [mailto:[EMAIL PROTECTED] > >>>> Sent: Monday, September 18, 2006 10:25 AM > >>>> To: Derby Discussion > >>>> Subject: Re: Insert large using SQL > >>>> > >>>> Thanks for response, but i have NO acces to database over JDBC, but > >>>> > >> only > >> > >>>> via text stream, thus i MUST use SQL commands (e.g. "INSERT INTO .... > >>>> (...) VALUES (...)" ). > >>>> I cannot call metgods of JDBC driver directly. > >>>> > >>>> > >>>> > >>>> > >>> Ok, > >>> Uhm, silly question. > >>> > >>> If you can access the database via a text stream, why can't you access > >>> > >> it > >> > >>> via JDBC? > >>> > >>> > >> because the database is on remote server, vhich comunicate via text > >> stream with client program. I have no direct access to this server. > >> At this time, we are using several other databases (Sybase ASE, Borland > >> JDataStore, Oracle, Hypersinic ...), and all them have method to insert > >> large texts. > >> We are testing the Derby database, because it is free, pure java, > >> simple, speed .... and this appears as only limitation to use it. > >> > > > > [mjs] > > Ok, > > So if I understand you... > > > > ClientA<--->ServerA<--->RDBMS > > > > Where, ClientA connects via TCP/IP to an app on ServerA that listens to > the > > port, passing the SQL statements to the RDBMS which resides on ServerA. > > > > Is this correct? > > If so, how is the app on ServerA communicating to the RDBMS? > > > Yes, it is correct. > ServerA communicating with RDBMS using JDBC, but it use only "limited" > subset of JDBC methodst (the system is desired to "universal as > possible"). > The server 'ServerA' does much more operations than only comunicate with > RDBMS. It is inpossible for us rewrite server at this moment. > > >
[mjs] You wouldn't have to "rewrite" your application. (Well, ok, that's making some assumptions...) A certain amount of code is going to be database centric. I'm going on an assumption that the Server side application is using JDBC's standard method(s) for writing a C/B/LOB to the database? If so, then it may make sense for you to review your design and to see how you're passing the data to your server side app. Even though its currently working with other databases, you may find that there's a better way so that any JDBC compliant databases will work. Again, I haven't seen your code, so take my observation with a grain of Kosher Salt.
