On Mon, 2014-10-27 at 09:17 +0100, Clemens Ladisch wrote:
> Tristan Van Berkom wrote:
> > locateFKeyIndex() function issuing the not-so-informative
> > message "foreign key mismatch" [...]
> >
> > o When foreign keys are enabled at CREATE TABLE time, it would
> > be very helpful at this
On 27 Oct 2014, at 8:17am, Clemens Ladisch wrote:
> Tristan Van Berkom wrote:
>> locateFKeyIndex() function issuing the not-so-informative
>> message "foreign key mismatch" [...]
>>
>> o When foreign keys are enabled at CREATE TABLE time, it would
>>be very helpful at
Tristan Van Berkom wrote:
> locateFKeyIndex() function issuing the not-so-informative
> message "foreign key mismatch" [...]
>
> o When foreign keys are enabled at CREATE TABLE time, it would
> be very helpful at this point to issue an error if a foreign
> key is declared which refers to
On 10/27/2014 01:49 PM, Tristan Van Berkom wrote:
This is just a request-for-enhancement bug report, I've went to the
trouble or reproducing this problem in a simple test case and while
I probably wont be able to immediately benefit from an upstream fix
for this, I hope that this bug report will
On Mon, 2014-10-27 at 15:49 +0900, Tristan Van Berkom wrote:
> This is just a request-for-enhancement bug report, I've went to the
> trouble or reproducing this problem in a simple test case and while
> I probably wont be able to immediately benefit from an upstream fix
> for this, I hope that
This is just a request-for-enhancement bug report, I've went to the
trouble or reproducing this problem in a simple test case and while
I probably wont be able to immediately benefit from an upstream fix
for this, I hope that this bug report will be perceived as helpful
and entered into your
6 matches
Mail list logo