[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
[eclipselink-users] generating SQL at compile time
|
- From: Mark Struberg <struberg@xxxxxxxx>
- Date: Thu, 30 Oct 2008 12:00:58 +0000 (GMT)
- Delivered-to: eclipselink-users@eclipse.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=aztio0MNZcr3rhEfKR6zlaXHKahCcGBNuipnBW5EI+pgdww2GPF9+u+TQJ/hZ3wBeyqUnHsjWEYTZA+hG/ftXprbkAiKgb0YK0Rw5Wb5hT5vXEtKAGKwGV+axvzOMurKHLsOatlTGMjvSrH8inBy/lahU8fVMwRbuqqOp0om2m4=;
Hi!
My first question, so please be gentle if I ask an obvious question (though I've searched web & markmail) ;)
I'm currently evaluating eclipseLink and a few other JPA providers for replacing JDO in our production systems.
In many production setups, the apps simply don't have any grants for create/alter table statements.
So, how can I generate the SQL statements for creating the database / upgrading the database without automatically performing those statements against the database?
Is there any class / ant task / maven plugin one can invoke to generate the SQL statements into a file?
How can I disable the schema execution at runtime?
txs in advance,
strub