"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> I asked my programmers to look into this. They think they have fixed
> it. I have asked them to provide me
> a patch. Should I post the patch here?
pgsql-patches is the usual place for patches.
I was planning to work on this myself tomorrow, so y
On Tue, Sep 16, 2003 at 00:38:10 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> I stuck a finger into the dike, but I think some people need to
> reconsider just how far they want to push "Informix compatibility".
> "#define date long" is certain to break and keep breaking our code,
> and doubtl
Tom Lane wrote:
(B>
(B> Dave Smith <[EMAIL PROTECTED]> writes:
(B> > If this is only dealing with constants, why not just explicitly add a
(B> > cast to the constant of the column type at the planner level. It would
(B> > solve this problem as well ...
(B>
(B> > create table test (f int2);
I'm working on adding support for unique indexes to the hash index code.
The majority of the code is finished, with the exception of the changes
to locking. My proposed changes are below -- if anyone sees a better way
to do things, let me know.
There's lots of info on the locking scheme used by ha
On Tue, 16 Sep 2003, Merlin Moncure wrote:
> I have been playing with temporary tables a little bit and noticed some
> interesting things.
Something else I've noticed about temp tables is that you are prohibited
from having a permanent table contain a foreign key reference to a temp
table, but
Hello,
I asked my programmers to look into this. They think they have fixed
it. I have asked them to provide me
a patch. Should I post the patch here?
Sincerely,
Joshua Drake
Bruce Momjian wrote:
I can confirm that this bug still exists in current CVS. The problem is
that "CREATE SCHEMA AUT
Dave Smith <[EMAIL PROTECTED]> writes:
> My point was that it was inconstant behavour. What exactly are you
> comparing with int2? To me the case without the cast should should throw
> the same error as the statement with the cast.
> select * from test where f=1981928928921;
I contend not. The
"Richard Hall" <[EMAIL PROTECTED]> writes:
> But if THIS solution is implemented then
> QUOTE('MyEndMarker')
> and
> MyEndMarker
> become noise words and it seems the parser could just assume to handle
> everything between
> CREATE FUNCTION ... AS
> and
> LANGUAGE
> as the delimite
Richard Hall wrote:
But if THIS solution is implemented then
QUOTE('MyEndMarker')
and
MyEndMarker
become noise words and it seems the parser could just assume to handle everything
between
CREATE FUNCTION ... AS
and
LANGUAGE
as the delimiters for a function definition.
But as that's so
tachuelita <[EMAIL PROTECTED]> writes:
> I was following an example on a book, and when I compiled it, it
> finishes with the error: 1075 Function Prototypes are an ANSI feature.
You forgot to use "-Ae" in the cc command line. HP's compiler has odd
ideas about which generation of C programmers us
My point was that it was inconstant behavour. What exactly are you
comparing with int2? To me the case without the cast should should throw
the same error as the statement with the cast.
Tom Lane wrote:
Dave Smith <[EMAIL PROTECTED]> writes:
If this is only dealing with constants, why not jus
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> ... In this case, I think the
> SQL spec was not thought out very well.
Many people think that about a lot of aspects of the spec ;-)
> I did not see a TODO item regarding global temporary tables...has this
> been attempted/done?
We concluded in the
On Mon, Sep 15, 2003 at 04:36:10PM -0400, tachuelita wrote:
> I was following an example on a book, and when I compiled it, it
> finishes with the error: 1075 Function Prototypes are an ANSI feature.
Huh, you need the real compiler from HP. The one bundled with the
operating system is apparently
"Tom Lane" writes:
>The SQL spec's notion of temp tables is only tenuously related to ours
>in the first place :-(. However, the spec appears to require that
>references to temp tables be unqualified names, so AFAICT it's not
>expected that applications can reference more than one schema's worth
Andreas said
>>
Well we might also have something like
CREATE FUNCTION ... AS QUOTE('MyEndMarker')
all the stuff
... MyEndMarker LANGUAGE 'plpgsql';
This looks quite SQL-like and should be easily implementable. Anyway,
this Perl-like style or Tom's proof-of-concept dollar-quoting one, both
s
as suggested by Andreas Pflug <[EMAIL PROTECTED]>
i send this to psql-hackers
- Forwarded message from Christian Ruediger Bahls <[EMAIL PROTECTED]> -
Date: Mon, 15 Sep 2003 18:43:17 +0200
Subject: Re: [BUGS] problem with libpq/encrypted
To: Tom Lane <[EMAIL PROTECTED]>
hello tom ..
.. i a
I was following an example on a book, and when I compiled it, it
finishes with the error: 1075 Function Prototypes are an ANSI feature.
What is this?.
I compile others programs and I haven´t got such problems.
Pls rspnd asap...
Regards
--
Posted via http://dbforums.com
---
Dave Smith <[EMAIL PROTECTED]> writes:
> If this is only dealing with constants, why not just explicitly add a
> cast to the constant of the column type at the planner level. It would
> solve this problem as well ...
> create table test (f int2);
> select * from test where f=cast('1981928928921'
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> The other and more interesting way is to manually jump into the
> temporary schema (eg. pg_temp_x) that hosts a temp table constructed by
> another backend. While this is unlikely to happen in a normal setting,
> the server does allow it. Following t
If this is only dealing with constants, why not just explicitly add a
cast to the constant of the column type at the planner level. It would
solve this problem as well ...
create table test (f int2);
select * from test where f=cast('1981928928921' as int2);
ERROR: pg_atoi: error reading "198192
Following tests were made in linux server running pg 7.4 beta 2.
I have been playing with temporary tables a little bit and noticed some
interesting things. I'm not sure if this is a part of the standard
canon or not but I thought it worth mentioning. Sorry if I'm bleating
out the obvious!
Acco
I discover that the following declaration inside
a stored procedure with postgres7.3 was legal:
a_variable ALIAS FOR$1;
note the missing space after FOR
now is not working anymore with 7.4beta
I don't know how much people will be affected,
may be is good wrote this in the migration note.
Regar
We've spent much effort trying to solve the "int8col = 42 doesn't use
an index" class of problems. AFAIR, all the recent tries have focused
on trying to get the parser to choose an index-compatible operator
initially. (In this example, that would mean promoting 42 to int8 so
that int8 = int8 woul
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > if ( !ret_value ) {
> > ereport(FATAL,
> > (errcode(ERRCODE_OUT_OF_MEMORY),
> > errmsg("strdup out of memory")));
> > }
>
> Sho
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> if ( !ret_value ) {
> ereport(FATAL,
> (errcode(ERRCODE_OUT_OF_MEMORY),
> errmsg("strdup out of memory")));
> }
Should be ERROR not FATAL (the places that are insisting
As suggested by Bruce Mojiman I'm working on
substitute some strdup not checked with xstrdup.
I seen that in the backend source tree there is no
xstrdup ( there is one in bin/psql tree) ,
I wrote it and inserted temporarelly in
backend/utils/mmgr/aset.c
I don't know exactly how work the error
26 matches
Mail list logo
