On 1/30/16 10:52 AM, Marko Tiikkaja wrote:
> On 2016-01-21 04:17, Simon Riggs wrote:
>> Marko, I was/am waiting for an updated patch. Could you comment please?
>
> Sorry, I've not found time to work on this recently.
>
> Thanks for everyone's comments so far. I'll move this to the next CF
> and
On 2016-01-21 04:17, Simon Riggs wrote:
Marko, I was/am waiting for an updated patch. Could you comment please?
Sorry, I've not found time to work on this recently.
Thanks for everyone's comments so far. I'll move this to the next CF
and try and get an updated patch done in time for that
On 5 January 2016 at 06:45, Simon Riggs wrote:
> On 4 January 2016 at 20:44, Alvaro Herrera
> wrote:
>
>
>> Maybe
>> there are more ALTER TABLE subcommands that should be setting something
>> up? In cases where multiple subcommands are being
2016-01-04 21:44 GMT+01:00 Alvaro Herrera :
> Pavel Stehule wrote:
> > 2015-10-05 0:08 GMT+02:00 Marko Tiikkaja :
> >
> > > In the past I've found the error message in cases such as this somewhat
> > > less helpful than it could be:
> > >
> > > =# CREATE
Pavel Stehule wrote:
> 2015-10-05 0:08 GMT+02:00 Marko Tiikkaja :
>
> > In the past I've found the error message in cases such as this somewhat
> > less helpful than it could be:
> >
> > =# CREATE TABLE qqq (a int);
> > =# CREATE UNIQUE INDEX IF NOT EXISTS qqq_a_idx ON qqq(a);
> >
On 4 January 2016 at 20:44, Alvaro Herrera wrote:
> Maybe
> there are more ALTER TABLE subcommands that should be setting something
> up? In cases where multiple subcommands are being run, it might be
> useful to see which one caused a certain error message.
>
I like
2015-10-05 0:08 GMT+02:00 Marko Tiikkaja :
> Hi,
>
> In the past I've found the error message in cases such as this somewhat
> less helpful than it could be:
>
> =# CREATE TABLE qqq (a int);
> =# CREATE UNIQUE INDEX IF NOT EXISTS qqq_a_idx ON qqq(a);
> =# ALTER TABLE qqq ALTER