Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 24 Jun 2011 22:59:47 +0000 (UTC)
From: "Julian Cable (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <919476780.38844.1308956387435.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2085191601.9388.1305274127477.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-3969) documentation for jdbc idempotent
 repository
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CAMEL-3969?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1305=
4732#comment-13054732 ]=20

Julian Cable commented on CAMEL-3969:
-------------------------------------

Shouldn't the primary key be (processorName,messageId) ?

And the back-ticks are MySql specific - the SQL standard is double quotes.

Julian

> documentation for jdbc idempotent repository
> --------------------------------------------
>
>                 Key: CAMEL-3969
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3969
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-sql
>    Affects Versions: 2.7.1
>         Environment: camels on win2k3, mysql(5.5.8) on win2k3
>            Reporter: Christoph Burmeister
>            Assignee: Christian M=C3=BCller
>              Labels: docuentation, idempotent, jdbc
>             Fix For: 2.8.0
>
>
> When running several camels with an idempotent repository (based on
> jdbc to mysql) I haven't found any documentation for the table-definition=
 or for changing parameters (like table-name).
> Getting through the sources, I tried out following definition on mysql th=
at works for me:
> CREATE TABLE IF NOT EXISTS `camel_messageprocessed` (
>  `messageId` varchar(255) NOT NULL,
>  `processorName` varchar(255) NOT NULL,
>  PRIMARY KEY (`messageId`)
> )
> Please check this back.
> =20

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira