Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 18396 invoked from network); 20 Jan 2010 21:54:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2010 21:54:58 -0000 Received: (qmail 22421 invoked by uid 500); 20 Jan 2010 21:54:57 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 22398 invoked by uid 500); 20 Jan 2010 21:54:57 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 22390 invoked by uid 99); 20 Jan 2010 21:54:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 21:54:57 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of clinton.begin@gmail.com designates 74.125.92.149 as permitted sender) Received: from [74.125.92.149] (HELO qw-out-1920.google.com) (74.125.92.149) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 21:54:46 +0000 Received: by qw-out-1920.google.com with SMTP id 5so306861qwf.60 for ; Wed, 20 Jan 2010 13:54:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=FLlQ/yUrPsoNazQhBseawoMOvEKdm56OOuhtY6G6S84=; b=ggkUIiRz1NxPeQcrKH/UoWi7bQK5OUrYkhrNW0eIt02iQY8O5b9UJCHnlNvtG5Z80i EUj9bzHMZDK+at2Nt6cs69v/lwT2qU714K/EKmfDLRfzL8Mo0080z51PCsHmOHYXr0vy gjz8cX+9EcLQ9mYyFd489HSum2GDC1HhFDHpc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Jjat+AKWiqL22g4K/qWOR/j11qWZwrGFOp2gW1ndn6TxqiDpOtrfwvbBXWbeWVYb52 Pcj4rqaAZ8Qq+giFGW92avPu/PB0u2FB/KoPUGeWXbjvstFgBbO6cLaIYtCRv1YV+OSX SB7a8PgFLeBM2mPmKyQljk4Ro0pas7vLlCKZ8= MIME-Version: 1.0 Received: by 10.224.53.23 with SMTP id k23mr378909qag.304.1264024461844; Wed, 20 Jan 2010 13:54:21 -0800 (PST) In-Reply-To: <4B5759A3.3010701@mchambliss.com> References: <4B5759A3.3010701@mchambliss.com> Date: Wed, 20 Jan 2010 14:54:21 -0700 Message-ID: <16178eb11001201354i33fe2084y87aad7fe37b0d130@mail.gmail.com> Subject: Re: Oracle PL/SQL with Schema Migrations From: Clinton Begin To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=00163613a360092888047d9fa13a X-Virus-Checked: Checked by ClamAV on apache.org --00163613a360092888047d9fa13a Content-Type: text/plain; charset=ISO-8859-1 You can configure the line terminator in the environment properties. Try a full line delimiter like "GO" On Wed, Jan 20, 2010 at 12:29 PM, Michael Chambliss wrote: > Hello, > > I just wanted to follow up on a question that was asked back in October: > > http://www.mail-archive.com/user-java@ibatis.apache.org/msg14957.html > > In summary, PL/SQL terminates lines with a semicolon, which causes problems > for the line delimiter logic in the migrations tool. Something like this: > > DECLARE > sometime date; > BEGIN > select sysdate into sometime from dual; > END; > > would fail on line 2. In a more realistic case, simply creating a function > or trigger would trip things up. Was this scenario later compensated for > via environment configuration options, or has anyone found a good work > around? > > Thanks! > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org > For additional commands, e-mail: user-java-help@ibatis.apache.org > > --00163613a360092888047d9fa13a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable You can configure the line terminator in the environment properties.=A0 Try= a full line delimiter like "GO"

On Wed, Jan 20, 2010 at 12:29 PM, Michael Chambliss <= ;email@mchambliss.com> wrote:
Hello,

I just wanted to follow up on a question that was asked back in October:
http://www.mail-archive.com/user-java@ibatis.apach= e.org/msg14957.html

In summary, PL/SQL terminates lines with a semicolon, which causes problems= for the line delimiter logic in the migrations tool. =A0Something like thi= s:

DECLARE
=A0sometime date;
BEGIN
=A0select sysdate into sometime from dual;
END;

would fail on line 2. =A0In a more realistic case, simply creating a functi= on or trigger would trip things up. =A0Was this scenario later compensated = for via environment configuration options, or has anyone found a good work = around?

Thanks!
Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org


--00163613a360092888047d9fa13a--