Mailing-List: contact ddlutils-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-user@db.apache.org
Received-SPF: pass (asf.osuosl.org: domain of tomdzk@gmail.com designates
 66.249.92.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Lm8O+TPQgHTidlaXEcLUBqzpi2rT1Mm3zHyG0CbD2mpZyN92BKkLI+6EpVzwYJPSbsG5wFK6ouoHLHmE5vl7EihHeYGjfvSHAy7zSIZ1HB1f3Pu9cUyD/AQuwb7TSgFk+onO8QgEVSEfjk4WtEDE0/TnPq58Qs45ghReDX5sTDM=
Message-ID: <224f32340603140223w60ecf5fau568ef603355ceab1@mail.gmail.com>
Date: Tue, 14 Mar 2006 11:23:56 +0100
From: "Thomas Dudziak" <tomdzk@gmail.com>
To: ddlutils-user@db.apache.org
Subject: Re: bug with drop column with firebird
In-Reply-To: <200603140859.28722.renaud.michel@defimedia.be>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200603140859.28722.renaud.michel@defimedia.be>

On 3/14/06, Renaud MICHEL <renaud.michel@defimedia.be> wrote:

> I just started looking at ddlutils, but encountered a small bug with
> firebird (and interbase as they are almost the same), when you drop a
> column the correct interbase syntax is
> ALTER TABLE tbl DROP col
> and do not accept a COLUMN keyword here.

Yep, database alteration is the next thing on the list.

> I provide a small patch (aigainst current svn) that implement the
> writeColumnDropStmt method for firebird and interbase.
> Should I create a new bug entry for this, or post such messages to the
> developper list?
> (I have some difficulties using that jira thing)

JIRA is definitely the the mechanism to use for bug reports and
submitting patches.
And its not so difficult. You first register, then you login and click
"Create New Issue" in the top menu. Next, you select DdlUtils as the
project and bug as the type. Now simply provide a short and a long
summary, select the component (core in your case).
You can also attach your patch there by navigating to the issue after
you've created it, and click on "Attach file" in the left menu.

cheers,
Tom