Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
MIME-Version: 1.0
In-Reply-To: <a3e2d20e-94dc-3a75-7acd-cef0329f1322@maniatis.org>
References: <CALAw18xqq_hHf9SRDKY+OQf_nM5v8KZncr29GoET5v7WBPXc4Q@mail.gmail.com>
 <bef91afd-ac41-5446-f22e-34874b1c6a52@maniatis.org> <CALAw18wK5NjOSMevjMqgxqY_v1sH6GkHKShEybvWAN3viRyVjA@mail.gmail.com>
 <CALAw18ymLgJkF6ocgiFxV018QCgbygdUUcFa8AUoLXxdJjuN_Q@mail.gmail.com>
 <6c4f15e9-414f-8dba-6fe4-ae540c5edf33@maniatis.org> <CAOy5kzNTSRHT0AYDG7pnepbPOJBioqv50S2XXBMTQwzar=ZV7A@mail.gmail.com>
 <FE066F12-324D-45D5-B0DD-8D00A996CC90@objectstyle.org> <0CF88A49-AA41-4160-9CE5-222582D38C83@objectstyle.org>
 <ffe22c03-4968-2794-e53a-8c34971d6ea2@maniatis.org> <AC408CB2-5B0F-4473-82EA-B3B8DFDDF164@objectstyle.org>
 <a3e2d20e-94dc-3a75-7acd-cef0329f1322@maniatis.org>
From: Michael Gentry <blacknext@gmail.com>
Date: Fri, 1 Jul 2016 09:20:02 -0400
Message-ID: <CAOy5kzPYEpWOZqp2eTTUqKYbgUHw2ymudbjzPpme8_xwm5NXEA@mail.gmail.com>
Subject: Re: Order of operations?
To: Cayenne Users <user@cayenne.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c05c72add4113053692d9ec
archived-at: Fri, 01 Jul 2016 13:20:43 -0000

--94eb2c05c72add4113053692d9ec
Content-Type: text/plain; charset=UTF-8

Constraints can get even more complex, like Oracle and PostgreSQL (perhaps
others) allow deferrable constraints, which are nice, but MySQL will blow
up immediately if a constraint fails even if it'll be satisfied by the end
of the transaction.


On Fri, Jul 1, 2016 at 9:09 AM, Aristedes Maniatis <ari@maniatis.org> wrote:

> On 1/07/2016 8:57pm, Andrus Adamchik wrote:
> >
> >> On Jun 30, 2016, at 11:04 PM, Aristedes Maniatis <ari@maniatis.org>
> wrote:
> >>
> >> 1. The Cayenne model will need to have additional metadata about
> database indexes and constraints. I've always liked that idea anyway but
> lacked the time to work on it personally. It could open up interesting
> interactions with projects like liquibase [1]
> >
> > We already have information about relationships (that are essentially FK
> constraints). Why do we need to know about indexes for ordering purposes?
>
> I was just thinking about db constraints really. For example, a unique
> index on a field (other than the PK) might need to be taken into
> consideration if you were deleting and creating records. The delete has to
> happen before the create, or they need to be coalesced into a single update.
>
> Ari
>
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>

--94eb2c05c72add4113053692d9ec--