"Alexander M. Pravking" <[EMAIL PROTECTED]> writes:
> If a column type is being changed with USING (NULL) clause,
> NOT NULL constraint seems not to be checked:
I've committed patches for this. Thanks for the report.
regards, tom lane
---(end of b
Ok, we checked our client code to eliminate this problem. Thanks for
the doc patch.
Regards,
Dirk
Simon Riggs wrote:
On Mon, 2006-07-10 at 13:35 +0200, Dirk Lutzebäck wrote:
In any case I would see this as a security problem because you cannot
control sql code injection easily
On Mon, 2006-07-10 at 13:35 +0200, Dirk Lutzebäck wrote:
> In any case I would see this as a security problem because you cannot
> control sql code injection easily (as with using DBD::Pg) if you have
> to pass parameters in the SQL string to use partial indexes.
That's not what I said. I see no
Hi Simon,
are you sure this has not been changed? I'm pretty sure my code worked
a while ago. We are using Perl DBD::Pg on the client side and almost
never pass parameters inside the SQL string for security reasons. I
can't say if it broke from 8.0 -> 8.1 for us or in one of the minor
8.1 rele
On Mon, 2006-07-10 at 12:22 +0200, Dirk Lutzebäck wrote:
> we are using postgresql 8.1.4 and found that partial indexes are not
> being used when the query is run using parameters, eg. in a function.
> When running the same query with arguments passed in the query string
> partial indexes are bein
Hi,
we are using postgresql 8.1.4 and found that partial indexes are not
being used when the query is run using parameters, eg. in a function.
When running the same query with arguments passed in the query string
partial indexes are being used.
here is the index:
CREATE INDEX c_6012_index ON
