On Fri, 2006-06-16 at 14:05 +0200, Paul J Stevens wrote:
> Fixed in trunk. Plz test.
A foreign key constraint cannot reference a myisam table.
ALTER TABLE dbmail_physmessage ENGINE=InnoDB;
fixed it for me. We should put this into the migration script.
Aaron
On Fri, 2006-06-16 at 17:56 -0700, Aaron Stone wrote:
> On Fri, 2006-06-16 at 14:05 +0200, Paul J Stevens wrote:
> > Fixed in trunk. Plz test.
>
> A foreign key constraint cannot reference a myisam table.
>
> ALTER TABLE dbmail_physmessage ENGINE=InnoDB;
>
> fixed it for me. We should put th
On Fri, 2006-06-16 at 17:56 -0700, Aaron Stone wrote:
> On Fri, 2006-06-16 at 14:05 +0200, Paul J Stevens wrote:
> > Fixed in trunk. Plz test.
>
> A foreign key constraint cannot reference a myisam table.
>
> ALTER TABLE dbmail_physmessage ENGINE=InnoDB;
>
> fixed it for me. We should put th
On Fri, 2006-06-16 at 17:56 -0700, Aaron Stone wrote:
> ALTER TABLE dbmail_physmessage ENGINE=InnoDB;
Now in SVN.
On Fri, 2006-06-16 at 18:38 -0700, Aaron Stone wrote:
> Jun 16 18:32:04 [dbmail/maintenance] Warning
> dbmail-message.c,dbmail_message_cache_subjectfield: no subject field
> value [300949]
>
> be at TRACE_MESSAGE so that they are not displayed by default. I bet
> it's mostly malformed spam that's
Paul J Stevens wrote:
Blake Mitchell wrote:
Is there appreciable overhead in just preparing each statement as it's
built and only using it once?
I guess we pretty much have to assume the penalty might be a potential DOS.
What penalty are we talking about here? The cost of preparrin
On Sat, 2006-06-17 at 04:30 -0400, Matthew T. O'Connor wrote:
> Paul J Stevens wrote:
> > Blake Mitchell wrote:
> >
> >> Is there appreciable overhead in just preparing each statement as it's
> >> built and only using it once?
> >>
> > I guess we pretty much have to assume the penalty migh
Aaron Stone wrote:
> On Fri, 2006-06-16 at 17:56 -0700, Aaron Stone wrote:
>> On Fri, 2006-06-16 at 14:05 +0200, Paul J Stevens wrote:
>>> Fixed in trunk. Plz test.
>> A foreign key constraint cannot reference a myisam table.
>>
>> ALTER TABLE dbmail_physmessage ENGINE=InnoDB;
>>
>> fixed it fo
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=367
==
Reported By:lkneschke
Assigned To:
===
