Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
I have documented this citext limitation with the attached, applied
patch.
Are you planning to insert similar verbiage into every other contrib
module's docs?
Uh, do they all have this odd behavior? Most people assume they would
get
On 03.06.2010 05:05, Bruce Momjian wrote:
The schema containing the typecitext/ operators must be
in the current varnamesearch_path/ (typically literalpublic/);
It's been a while, but the way I read my own example is that the schema
containing the citext operators being in the current
Markus Wichitill wrote:
On 03.06.2010 05:05, Bruce Momjian wrote:
The schema containing the typecitext/ operators must be
in the current varnamesearch_path/ (typically literalpublic/);
It's been a while, but the way I read my own example is that the schema
containing the citext operators
Robert Haas wrote:
On Fri, Mar 5, 2010 at 5:24 AM, Markus Wichitill ma...@gmx.de wrote:
The following bug has been logged online:
Bug reference: ? ? ?5364
Logged by: ? ? ? ? ?Markus Wichitill
Email address: ? ? ?ma...@gmx.de
PostgreSQL version: 8.4.2
Operating system: ? Linux,
Bruce Momjian br...@momjian.us writes:
I have documented this citext limitation with the attached, applied
patch.
Are you planning to insert similar verbiage into every other contrib
module's docs?
regards, tom lane
--
Sent via pgsql-bugs mailing list
On Fri, Mar 5, 2010 at 5:24 AM, Markus Wichitill ma...@gmx.de wrote:
The following bug has been logged online:
Bug reference: 5364
Logged by: Markus Wichitill
Email address: ma...@gmx.de
PostgreSQL version: 8.4.2
Operating system: Linux, Win7
Description:
The following bug has been logged online:
Bug reference: 5364
Logged by: Markus Wichitill
Email address: ma...@gmx.de
PostgreSQL version: 8.4.2
Operating system: Linux, Win7
Description:citext behavior when type not in public schema
Details:
Comparisons with