Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of michaelm001@frontiernet.net
 designates 66.133.182.167 as permitted sender)
Message-ID: <437812E1.5070106@frontiernet.net>
Date: Sun, 13 Nov 2005 20:30:25 -0800
From: Michael McCutcheon <michaelm001@frontiernet.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: derby-user@db.apache.org
Subject: stored procedures and embedded derby
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello All,

I'm going to be using Derby (in embedded mode) in Tomcat for my web 
app.  I am building everything from scratch.

I'm trying to decide on if I want to put 'everything' in stored 
procedures or just code stuff in the application. (i.e. no SQL in the 
application code whatsoever, all logic in procedures, etc.)

It seems like stored procedures are just more developer work for an 
embedded database (more stuff to setup), and may actually be slower at 
runtime because (I assume) the static methods are called reflectively 
(correct me if I am wrong).

However, if I did do everything in stored procedures, that would make it 
easy if I were to move out of embedded and put the database on a 
seperate machine.

But for now the plan is to be completely embedded.

Can anyone share thoughts on this?  What do you think are the 
benefits/drawbacks of stored procedures for an embedded database?

Thanks for any input,

Mike