db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Dohman" <B-Doh...@gotcg.net>
Subject RE: threads and derby
Date Thu, 17 Apr 2008 17:38:16 GMT
To answer your question, can you elaborate on how you access your database?
For instance:
 a) Are you using a single or multiple connections?

-- I'm using just one server to connect to the database.  All transactions on the database
will go through this server, nothing else will have access to it.

 b) Is autocommit used, or are you committing your transactions explicitly?
-- In regards to this question I'm unsure of which I am using, as I haven't came across this
before.  I'm still fairly new to java and derby so I am not sure exactly what I would be using.
 Basically my process was to install derby, then setup my username/password and all my tables
through netbeans.  If there is more setup process that needs to be done, I haven't come across
it yet.



-----Original Message-----
From: Kristian.Waagan@Sun.COM [mailto:Kristian.Waagan@Sun.COM] 
Sent: Thursday, April 17, 2008 12:32 PM
To: Derby Discussion
Subject: Re: threads and derby

Brandon Dohman skrev:
>
> I’ve currently created a multithreaded server that is using 1 class to 
> do all of the database interactions when receiving commands from the 
> client programs.
>
>  
>
> My question:  When my server code has multiple threads going, will the 
> database, or the java code for that matter, wait until the current 
> threads transactions are done before allowing another thread to take 
> control of the database?
>
>  
>
> I have created a simple user login system that allows access to a 
> machine, and there will be possible multiple logins going on at the 
> same time (very possible it will never happen at the exact same time) 
> but along with logins, admin users will be updating information in the 
> database.  And I just want to make sure I won’t crash my database, if 
> I have operations trying to access things at the same time.
>
Hello Brandon,

In general, Derby is thread safe and supports multiple connections / users.
Concurrent accesses will be synchronized internally to avoid data 
corruption and other problems.

To answer your question, can you elaborate on how you access your database?
For instance:
 a) Are you using a single or multiple connections?
 b) Is autocommit used, or are you committing your transactions explicitly?

If you answer these questions, I'm sure you will get more feedback.


regards,
-- 
Kristian

>  
>
> Thanks
>
> B
>
>
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.519 / Virus Database: 269.23.0/1381 - Release Date: 
> 4/16/2008 9:34 AM
>


No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.519 / Virus Database: 269.23.0/1381 - Release Date: 4/16/2008 9:34 AM
 

No virus found in this outgoing message.
Checked by AVG. 
Version: 7.5.519 / Virus Database: 269.23.0/1381 - Release Date: 4/16/2008 9:34 AM
 

Mime
View raw message