Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion cascade delete emulation

Received: by 10.52.74.197 with SMTP id w5mr1100787vdv.4.1344331563771;
        Tue, 07 Aug 2012 02:26:03 -0700 (PDT)
X-BeenThere: propel-development@googlegroups.com
Received: by 10.52.100.135 with SMTP id ey7ls86525vdb.6.gmail; Tue, 07 Aug
 2012 02:26:03 -0700 (PDT)
Received: by 10.52.67.167 with SMTP id o7mr3575161vdt.1.1344331563419;
        Tue, 07 Aug 2012 02:26:03 -0700 (PDT)
Received: by 10.52.67.167 with SMTP id o7mr3575160vdt.1.1344331563379;
        Tue, 07 Aug 2012 02:26:03 -0700 (PDT)
Return-Path: <josselin.jacqu...@gmail.com>
Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53])
        by gmr-mx.google.com with ESMTPS id y20si2894844vdd.0.2012.08.07.02.26.03
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 07 Aug 2012 02:26:03 -0700 (PDT)
Received-SPF: pass (google.com: domain of josselin.jacqu...@gmail.com designates 209.85.212.53 as permitted sender) client-ip=209.85.212.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of josselin.jacqu...@gmail.com designates 209.85.212.53 as permitted sender) smtp.mail=josselin.jacqu...@gmail.com; dkim=pass header...@gmail.com
Received: by vbbfc26 with SMTP id fc26so1934759vbb.26
        for <propel-development@googlegroups.com>; Tue, 07 Aug 2012 02:26:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=afE0IeGhUrAdqM+8po2Ctx98v6M5eucOAFWqeNdi1Ig=;
        b=jTFFb/qQL7q9XDMgul0sK9KPpcQNe6snnBCZo9tGiNxFSs6yrQ8Mk2Pa5Xwot5cCtz
         HZv4cm22oWrEo03cyRTMky7vwfmLgOFpIt/jjqFRnUWqVhKCSq7Uq6dibZ3+duA8Tsbe
         EVxIGdykNdWRNvoRg49UppAxJGa1W4C8gMDKiJabVPRdNFy2MGtbiVxmj83bMKDiyPi9
         1UQ6m9/j8bnykeGo9W9quMXNPw4ULhsbJ3c9mz2Sg3z1vrXx8mPiWS+x41Y1HN2ABncx
         4YfxgKpmVMh7xt/slkOCicvsxy8AliCjuxExPuZADwnBRpziL3Lp0U6J7+gxkikpejNk
         JgFw==
MIME-Version: 1.0
Received: by 10.52.21.174 with SMTP id w14mr9038899vde.24.1344331563259; Tue,
 07 Aug 2012 02:26:03 -0700 (PDT)
Received: by 10.220.96.72 with HTTP; Tue, 7 Aug 2012 02:26:03 -0700 (PDT)
Date: Tue, 7 Aug 2012 11:26:03 +0200
Message-ID: <CANJiqQDjQcbMVC-z3J0F8j6g6mM5e=ubBr4jtyAsFdoEb0L...@mail.gmail.com>
Subject: cascade delete emulation
From: Josselin Jacquard <josselin.jacqu...@gmail.com>
To: propel-development@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi, I got almost all the runtime tests of propel 1.6 passing onto
sqlite. II spent quite a lot of time into it. Also I made some change
to the dbSqlite adapter because of the rowcount being ineffective for
select unbeffered queries with the sqlite pdo driver.

But one of the problems is the delete tests : the tests make the
assumption that there is no cascade delete emulation. But for sqlite
there is emulation. Appart from testing the class of the dbAdapter, is
there a way to make a clean detection of cascade emulation being
enabled at runtime ? That w=E8uld be better than testing the dbAdapter
Class.

Bye

Joss