Return-Path: X-Original-To: apmail-empire-db-commits-archive@www.apache.org Delivered-To: apmail-empire-db-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D780210CA3 for ; Tue, 7 May 2013 08:09:22 +0000 (UTC) Received: (qmail 66160 invoked by uid 500); 7 May 2013 08:09:22 -0000 Delivered-To: apmail-empire-db-commits-archive@empire-db.apache.org Received: (qmail 66073 invoked by uid 500); 7 May 2013 08:09:19 -0000 Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: empire-db-dev@empire-db.apache.org Delivered-To: mailing list commits@empire-db.apache.org Received: (qmail 65942 invoked by uid 500); 7 May 2013 08:09:16 -0000 Delivered-To: apmail-incubator-empire-db-commits@incubator.apache.org Received: (qmail 65926 invoked by uid 99); 7 May 2013 08:09:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 08:09:16 +0000 Date: Tue, 7 May 2013 08:09:15 +0000 (UTC) From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?= To: empire-db-commits@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (EMPIREDB-182) Wrong datatype for uniqueid in SQLServer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Rainer D=C3=B6bele created EMPIREDB-182: -------------------------------------- Summary: Wrong datatype for uniqueid in SQLServer Key: EMPIREDB-182 URL: https://issues.apache.org/jira/browse/EMPIREDB-182 Project: Empire-DB Issue Type: Bug Components: Core Reporter: Rainer D=C3=B6bele Assignee: Rainer D=C3=B6bele Priority: Minor Fix For: empire-db-2.4.2 The correct datatype identifier f=C3=BCr uniqueid in SQL Server is UNIQUEID= ENTIFIER instead of UNIQUEID. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira