lumn (presumably movieid) is aliased as "nolock". The
following query probably would have worked (not that I'm recommending
it):
select * from netflix.ratings with (nolock) where nolock = ...
--
Michael Fuhr
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
.1 changed UNICODE to UTF8
and added support for 4-byte characters, so the fact that the error
says "UNICODE" and your database doesn't appear to support 4-byte
characters makes me wonder if you're running 8.0 or earlier.
--
Michael Fuhr
--
Sent via pgsql-bugs mailing li
s to
> > calculate.
>
> I thought it was the exact opposite, quoting from RFC1321:
And if you *do* need cryptographic security then don't use MD5, and
consider using SHA-256 instead of SHA-1. See RFC 4270 for discussion.
ftp://ftp.rfc-editor.org/in-
that value in an integer column? I don't think PostgreSQL
supports numbers in non-Latin scripts unless your underlying strtol()
and sprintf() functions do.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
On Tue, Jun 19, 2007 at 02:55:07PM +0530, Murali Doss wrote:
> No result but the matching data is available in table
What values are not matching that you expect to match? Can you
provide a reproducible test case? What are your locale settings
and encoding?
--
Michael F
ps that somebody could perform to see
the same thing you're seeing.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
;show client_min_messages"?
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
sparc-sun-solaris2.9, compiled by GCC gcc (GCC) 3.4.2
(1 row)
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
in at least one
of the constrained columns."
This has been discussed before; search the archives for words like
"null", "unique", and "comparison" or "compare".
--
Michael Fuhr
---(end of broadcast)-
serting NULL into the column(s) with the unique
index?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message c
ostgres.c:1004
#10 0x005864ee in PostgresMain (argc=4, argv=0x8844a8,
username=0x884390 "mfuhr") at postgres.c:3232
#11 0x0055c31a in ServerLoop () at postmaster.c:2863
#12 0x0055d90a in PostmasterMain (argc=5, argv=0x8828c0) at
postmaster.c:941
#13 0x0051d5e3 in main (argc=5, argv=0x8828c0) at main.c:265
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
en uses LIKE. Locale-specific
regular expression patterns still do not work in these encodings.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Wed, Dec 13, 2006 at 08:34:38AM -0700, Michael Fuhr wrote:
> On Wed, Dec 13, 2006 at 03:03:43PM -, Jean-Gérard Pailloncy wrote:
> > On PostgreSQL 8.1.2
> > select -32768::smallint
> > throws the error
> > ERROR: smallint out of range
>
> I think the cast
t)
which is why you're getting "smallint out of range." This should work:
select (-32768)::smallint
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
active/plpgsql-structure.html
"Functions and trigger procedures are always executed within a
transaction established by an outer query -- they cannot start or
commit that transaction, since there would be no context for them
to execute in."
--
Michael Fuhr
---(end of broa
(but are you sure this is not a PostGIS bug?) ...
What does "SELECT postgis_full_version()" show? If you still have
the 8.1.3 system then please post the output from both 8.1.3 and
8.1.4.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
t;DEALLOCATE \"MyQuery\"");
See "Identifiers and Key Words" in the "SQL Syntax" chapter of the
documentation for more information about quoted identifiers.
http://www.postgresql.org/docs/8.1/interactive/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
--
Michael Fuhr
--
our own functions in PL/pgSQL or C or some other language
and create operators that call those functions. Such customizations
survive migrations via database dumps so you don't have to remember
to patch the code every time you upgrade.
If you're working with spatial data then you
r |
test=> SELECT test();
test
--
(1 row)
test=> \d foo
Table "public.foo"
Column | Type | Modifiers
----+-+---
id | integer |
newcol | integer |
--
Michael Fuhr
---(end of broadcast)--
w.
As Tom Lane already pointed out, you're probably needing a WHERE
clause. Does this do what you want?
SELECT ia.name, iac.internal
FROM information_assets AS ia
LEFT OUTER JOIN information_asset_categories AS iac ON ia.category_id = iac.id
WHERE ia.id = 21;
--
M
part of the outer join condition
that restricts rows from information_asset_categories (T2); it
doesn't restrict rows from information_assets (T1). If you don't
want all rows from information_assets then why are you using an
outer join?
--
Michael Fuhr
---(end
exactly those column names that appear in both
input tables."
http://www.postgresql.org/docs/8.1/interactive/sql-select.html#SQL-FROM
"NATURAL is shorthand for a USING list that mentions all columns
in the two tables that have the same names."
--
Michael Fuhr
-
polygon as one of the parameters to overlaps()?
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
pg_database;
Do the server logs contain any unusual messages? Have you had any
hardware problems or system crashes?
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ny arguments and that
it's waiting to read from standard input (the terminal window)? If
the dump file contains SQL statements then why are you using
pg_restore instead of psql?
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below
On Fri, Jun 16, 2006 at 06:53:28AM -0600, Michael Fuhr wrote:
> The query plan shouldn't affect psql's behavior but selecting
> different columns might. Notice that the estimated column width
> is much higher when you select the geometry column than when you
> don't:
oadable from http://www.faunalia.it/download/bug2481.tar.gz
A HEAD request against that file shows it to be 116M (121747346),
not 16M, and it appears to be on a slow link (curl estimates over
an hour to download). Can you create a smaller test case?
--
Michael Fuhr
-
re beneath it? If not then you might need to adjust your
coredumpsize resource limit.
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
aren't relevant -- the problem is
due to using the same label to refer to multiple things. Use different
names for the variables or qualify the column names in the query
("SELECT t.symbol, t.rs03, t.rs12, t.peg FROM testbug AS t ...").
--
Michael Fuhr
---(en
ot;
Apparently a new row's tableoid isn't set until the row is actually
inserted. Tableoid would be set in an AFTER trigger, but if the
intent is to prevent inheritance then enforcing the constraint with
a trigger on the base table wouldn't work because triggers aren't
inherited.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
ssion? Are you using connection pooling?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
ning the above query.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
5077;
SET enable_seqscan TO off;
SET enable_indexscan TO on;
SELECT ctid, xmin, xmax, * FROM hierarchy WHERE id >= 5077;
SELECT ctid, xmin, xmax, * FROM hierarchy WHERE id = 5077;
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.
re those transactions using? A SERIALIZABLE
transaction won't see data committed by other transactions after
its snapshot has been taken.
If none of this helps then could you post a series of steps that
somebody could use to duplicate the problem?
--
Michael Fuhr
--
or its operations will be rolled back unless you
protect them with savepoints.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
last number.
http://www.postgresql.org/docs/faqs.FAQ.html#item4.11.4
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
n). According to past discussion it's
per the spec.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message
OT IN (SELECT a_id FROM b WHERE a_id IS NOT NULL);
id
2
(1 row)
According to past discussion this behavior is per the SQL specification.
Search the list archives for more information.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
o-phase commit? Why do you think it's "surely"
involved? Let's see a complete test case before jumping to
conclusions.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
what earlier command failed and why.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Wed, Feb 15, 2006 at 02:28:33PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Did you test OpenSSL builds?
>
> Nope, I did not, and that's a good point. Will try again with openssl.
My non-OpenSSL build shows no memory leak, so the l
On Wed, Feb 15, 2006 at 01:43:18PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I can reproduce this in 8.1.3 on FreeBSD 6.0 and Solaris 9. Here's
> > a standalone test case:
>
> > SELECT crypt(x::text, '$1$salt') FROM gene
ing the query with 'salt' instead of '$1$salt' doesn't exhibit
a memory leak, not even with more iterations from generate_series.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
ld
add weight to Tom's suggestion that an old libpq might be responsible.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
that somebody updated an existing record? How many times has
the problem happened? If more than once, how often? Can you think
of anything that happened with the database around the time the
problem started? Have you enabled statement logging to see what
statements are actually being executed?
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
a way to tell pg_query and
friends that you want binary results, you could retrieve the binary
image data without having to mess with encoding and decoding.
Even if you're satisfied with what you're doing, it would be
interesting to find an explanation for pg_unescape_bytea's perfor
at
does something like the following show?
$tstart = microtime(true);
$data = pg_unescape_bytea(pg_fetch_result($res, 'data'));
$dt = microtime(true) - $tstart;
header("Content-Type: text/plain");
printf("unescape time = %.3fms, %d bytes\n", $dt * 1000.0, strlen($data)
lete program so we can see everything
you're doing. You might also try asking in the pgsql-jdbc list to
see if anybody there has heard of this problem.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
uot;xyz" at character 12
LINE 1: SELECT abc xyz FROM foo;
^
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ocumentation
> hasn't been modified.
Sequences don't roll back so they can have holes; that's long-standing
behavior that hasn't changed. Can you provide a test case that
behaves differently in different versions of PostgreSQL?
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
indexed and individual execution
> of each query is very fast.
Could you post the EXPLAIN ANALYZE output of each query? Have you
tuned any of your postgresql.conf settings, in particular shared_buffers?
How much memory do you have?
--
Michael Fuhr
---(e
es during transactions."
> To get again the right date, it is necessary do disconnect and reconnect.
Do you have autocommit disabled? I'd guess all of your function
calls are happening in the same transaction. You shouldn't have
to reconnect; starting a new transaction shou
ression "1 NOT IN (2,NULL,3)" evaluates to NULL because NULL
means "unknown." This comes up occasionally; see the archives for
past discussion.
http://archives.postgresql.org/pgsql-sql/2005-12/msg00219.php
http://archives.postgresql.org/pgsql-sql/2005-10/msg00227.php
--
Micha
nstalled)?
What does "SHOW log_statement" show? Are you sure you're looking in
the right log file? Do you see other log entries?
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ow up in the server logs? What operating system
and version? What version of PostgreSQL and where did you get it
(installed a package, built it yourself from source, etc.)? If you
got a core dump, can you get a stack trace from it?
--
Michael Fuhr
-
version
you're running? DISABLE TRIGGER is in the documentation for 8.1
but not for 8.0.
http://www.postgresql.org/docs/8.0/interactive/sql-altertable.html
http://www.postgresql.org/docs/8.1/interactive/sql-altertable.html
--
Michael Fuhr
-
eks ago:
http://archives.postgresql.org/pgsql-bugs/2005-12/msg00128.php
http://archives.postgresql.org/pgsql-committers/2005-12/msg00296.php
http://archives.postgresql.org/pgsql-committers/2005-12/msg00297.php
--
Michael Fuhr
---(end of broadcast)---
TIP 5: d
is saying? The commit message he posted had a
date of 2005-11-28; 8.1.1 wasn't tagged until 2005-12-08.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
an't call method "reval" on an undefined value at line
> 1.
Can you use the Safe module in standalone Perl scripts? What happens
if you run the following?
#!/usr/bin/perl
use strict;
require Safe;
print "Safe::VERSION = $Safe::VERSION\n";
my $foo = new Safe(&
ESCE(col1, '') || COALESCE(col2, '') FROM foo;
col1 | col2 | ?column?
--+--+--
aaa | bbb | aaabbb
ccc | | ccc
| ddd | ddd
(3 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
[Please copy the mailing list on replies.]
On Thu, Dec 15, 2005 at 07:32:54PM +0100, Adam Kolany wrote:
> Michael Fuhr napisa?(a):
> >On Thu, Dec 15, 2005 at 11:03:55AM +, Adam Kolany wrote:
> >>stoff=> select sum(wplyw),sum(wydatek), sum(wplyw)-sum(wydatek) from
>
| sum | ?column?
> ---+-+--
> 73745 | 6712.55 | 67032.5
> (1 row)
What data types are wplyw and wydatek?
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
section of code that it
protects.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
is option
is not a general fix for bad programming." It would be better to
use standard-conforming expressions such as IS DISTINCT FROM (standard
since SQL:1999, as I recall).
test=> SELECT NULL = NULL;
?column?
--
(1 row)
test=> SELECT NULL IS DISTINCT FROM NULL;
rgv=0x82e4d98, username=0x82e4d78
"mfuhr") at postgres.c:3168
#10 0x081684e6 in ServerLoop () at postmaster.c:2853
#11 0x08169a01 in PostmasterMain (argc=3, argv=0xbfbfecb8) at postmaster.c:943
#12 0x08133612 in main (argc=3, argv=0xbfbfecb8) at main.c:256
--
Michael Fuhr
---
1563.php
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
equire functions to issue a RETURN statement (Tom)
This is a byproduct of the newly added OUT and INOUT functionality.
RETURN can be omitted when it is not needed to provide the function's
return value.
--
Michael Fuhr
---(end of broadcast)-
to_char('13:00:00'::interval,'HH:MM AM');
ERROR: invalid format specification for an interval value
HINT: Intervals are not tied to specific calendar dates.
This looks like the commit that changed the behavior in 8.1 (the
hint was added later):
http://archives.postgresql
('test1_id_seq'). That expression is used in
both inserts, so the sequence gets incremented twice. See the
archives for numerous past discussions of this behavior.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions be
on test1:
CREATE RULE test1_on_insert AS ON INSERT TO test1
DO INSERT INTO test_log1 (qid) VALUES (new.id);
This "gotcha" comes up occasionally; it's due to the fact that rules
are macros. Search the archives for past discussion.
--
Michael Fuhr
w.movable-type.co.uk/scripts/GIS-FAQ-5.1.html
If you're working with geospatial data then you might want to look
at PostGIS.
http://postgis.refractions.net/
See also PostgreSQL's contrib/earthdistance module.
--
Michael Fuhr
---(end of broadcast)---
gresql.org/pgsql-hackers/2004-10/msg00766.php
http://www.postgresql.org/docs/faqs.TODO.html
In the first message above, Tom Lane suggests hacking
src/backend/utils/adt/datetime.c if you want to fix your own system.
--
Michael Fuhr
---(end of broadcast)-
d post it here. Use "q" to exit
gdb. If Tom Lane gives differing or additional instructions then
listen to him, because he's one of the core developers.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
third-party modules, etc.?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailin
-07
(1 row)
test=> SELECT '2005-10-29 12:00:00-06'::timestamptz + '1 day'::interval;
?column?
2005-10-30 12:00:00-07
(1 row)
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In vers
iled by GCC gcc
(GCC) 3.4.2
now | 2005-10-25 13:35:47.104595+10
?column? | 2005-11-01 13:35:47.104595+11
?column? | 2005-11-01 14:35:47.104595+11
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
is problem (i can send you these files).
A test case would be useful: all SQL statements, data, and other
steps that somebody could use to duplicate what you're doing.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you
to use dblink to make another connection
to the database from within the function and execute transactions
over that connection.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ages based
on entries in a template table (pg_pltemplate).
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On Thu, Oct 13, 2005 at 09:49:20AM -0600, Michael Fuhr wrote:
> ecpg in 8.0.4 seems not to like the macros. I get the same error,
> but not if I do this:
>
> VARCHAR t[256];
> VARCHAR o[256];
>
> ecpg in 8.1beta3 works either way.
This appears to be the guilty c
inter to varchar are not implemented
> tenant.ec:376: ERROR: pointer to varchar are not implemented
ecpg in 8.0.4 seems not to like the macros. I get the same error,
but not if I do this:
VARCHAR t[256];
VARCHAR o[256];
ecpg in 8.1beta3 works either way.
--
Michael Fuhr
-
d data from your first message;
about the only differences from what you're doing are that the table
isn't inherited and it uses "COPY foo FROM stdin" instead of reading
the data from an external file. If this test works correctly, what
happens if you use "COPY FROM stdin&q
On Wed, Oct 12, 2005 at 08:17:23PM +0100, Oliver Elphick wrote:
> On Wed, Oct 12, 2005 at 12:19:41PM -0600, Michael Fuhr wrote:
> > Could you post the table definitions?
>
> Here it is:
I created the tables you posted (sans foreign key constraints because
you didn't in
On Wed, Oct 12, 2005 at 08:23:15PM +0100, Oliver Elphick wrote:
> On Wed, 2005-10-12 at 12:13 -0600, Michael Fuhr wrote:
> > On another note, regarding the following:
> >
> > > invdate | date | not null default
> > > ('now&#x
On Wed, Oct 12, 2005 at 12:19:41PM -0600, Michael Fuhr wrote:
> On Wed, Oct 12, 2005 at 07:08:20PM +0100, Oliver Elphick wrote:
> > I should add that the table inherits from another one, but the
> > swapped columns are a long way into the extra columns specific to
> > this
plpython is listed there ...
I don't know about the plperl or pltcl problems, but are you sure
"plpython" is in pg_pltemplate? "plpythonu" should be there but
not "plpython", at least not in a distribution built from the
unmodified source code.
--
Michael Fuhr
---
On Wed, Oct 12, 2005 at 07:08:20PM +0100, Oliver Elphick wrote:
> I should add that the table inherits from another one, but the
> swapped columns are a long way into the extra columns specific to
> this table.
Could you post the table definitions?
--
Mic
| not null default ('now'::text)::date
Are you sure you want 'now'::text as a default, considering the
warning against it?
http://www.postgresql.org/docs/8.0/interactive/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT
--
Michael Fuhr
-
PGUSER environment variable instead of using the -U option?
You mentioned FC4, so maybe Tom Lane or somebody more familiar
with that platform has some ideas about what's happening.
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
lp" for more information.
Use the --help option or consult the createlang documentation to see
the correct order of options and arguments. It works fine here with
.pgpass if the syntax is correct; have you run "createlang --version"
to verify that you're running the
l.org/docs/7.4/interactive/release-7-4.html
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
nations of the problems of using binary floating-point
numbers.
If you need exact results then use the numeric type.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
insert significant trailing
spaces into a VARCHAR column if the client library strips them?
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
autovacuum
autovacuum_vacuum_cost_delay
archive_command autovacuum_analyze_scale_factor
autovacuum_vacuum_cost_limit
australian_timezones autovacuum_analyze_threshold
autovacuum_vacuum_scale_fa
On Sun, Sep 11, 2005 at 03:03:57AM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > What do other DBMSs do?
>
> This is a fair question. Given that the SQL committee hasn't provided
> any useful leadership, what are other groups doing?
I d
On Sun, Sep 11, 2005 at 12:43:58AM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Apparently the two intervals don't cancel each other out (i.e.,
> > they're not optimized to zero),
>
> Well, no, because + and - associate left-to
ing? Could the data have been inserted and then deleted?
Might the inserting transaction have been rolled back? Do you have
any triggers that might be silently discarding the insert?
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions b
Y field of the or .
and General Rule 6b says
If, after the preceding step, any of the
result is outside the permissible range of values for the field
or the result is invalid based on the natural rules for dates and
times, then an exception condition is raised: data exception --
datetime
significant. The server makes the decision, not the ECPG preprocessor
or library, which simply passes the value to the server.
If you think this behavior should be changed then propose it on
pgsql-hackers and discuss it with the developers.
--
Michael Fuhr
---(end of broadc
t behavior, and also doesn't match Oracle's
> behavior, we are requesting a fix or an option.
Identifiers are NAME types, not CHAR types; the difference in
behavior is no more inconsistent than that between VARCHAR and CHAR.
If the strings have trailing spaces but the identifiers on
1 - 100 of 291 matches
Mail list logo
