Re: delimiter problem with initial sql

On Mar 17, 5:22 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > ... > Sorry, not much encouragement for you there, but if you have any bright, > truly database-portable ideas, we'd love to hear them. > I've the same problem and run a separate scripts is annoying, maybe a solution should be

Re: delimiter problem with initial sql

Hi Malcolm! >> I'm using initial sql data to create some triggers in MySQL. This >> works fine until I use multiple statements in a trigger. > There's no clean fix that just uses the Django framework at the moment. > This is a really hard problem to solve in the general case, since it > would req

Re: delimiter problem with initial sql

On Sat, 2007-03-17 at 06:49 -0700, Indy wrote: > Hello all! > > I'm using initial sql data to create some triggers in MySQL. This > works fine until I use multiple statements in a trigger. MySQL makes > it necessary to change the statement delimiter, because multiple > trigger statements must be

delimiter problem with initial sql

Hello all! I'm using initial sql data to create some triggers in MySQL. This works fine until I use multiple statements in a trigger. MySQL makes it necessary to change the statement delimiter, because multiple trigger statements must be separated by a semicolon. The problem is, that django separ