On Tue, Jan 06, 2004 at 11:38:44PM -0500, Tom Lane wrote:
> AFAICS, Alex is quite far out in left field to believe that this is a
> standard notation. The fact that some BSD platforms have accepted it
How did I know you'd say that, Tom?
By "standard," I mean, "many people use it." Not, "some st
On Tue, 6 Jan 2004, Tom Lane wrote:
> > Does this complete this TODO?
> > o Allow parameters to be specified by name and type during
> > definition
>
> Uh, no; the lack of documentation updates being one of the more glaring
> omissions. I should think that psql's \df needs some tho
"Alex J. Avriette" <[EMAIL PROTECTED]> writes:
> In how many places are we using inet_aton?
BTW, further digging shows that when the platform has neither
getaddrinfo nor inet_aton, we fall back to src/port/inet_aton.c,
which is a BSD-derived bit of code that behaves exactly as per
your man page qu
"Alex J. Avriette" <[EMAIL PROTECTED]> writes:
> I really think this is the wrong way to approach it. The 127.1
> convention is common, and valid.
AFAICS your own platform's C library doesn't support it, which means
you are on pretty shaky ground to make this claim.
regard
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> 1. clarification of my IRC comment: A quick examination seems to shaw
> that we use the native getaddrinfo() where it exists, otherwise we use
> our own, which in turn calls inet_ntoa().
> 2. ip6 has a well defined standard for abbreviation, and is qui
On Tue, Jan 06, 2004 at 10:52:19PM -0500, Andrew Dunstan wrote:
> 4. My personal preference would be that if any change is made it would
> be to insist on an unabbreviated dotted quad for ip4. Alternatively, we
I really think this is the wrong way to approach it. The 127.1
convention is common,
Dave Cramer <[EMAIL PROTECTED]> writes:
> So how can I create a function that it will choose, the option of
> casting is not available to me
If the inputs are all unknown, I think your only choice is to not have
more than one function of that name (and number of parameters).
Otherwise the system s
A few points.
1. clarification of my IRC comment: A quick examination seems to shaw
that we use the native getaddrinfo() where it exists, otherwise we use
our own, which in turn calls inet_ntoa().
2. ip6 has a well defined standard for abbreviation, and is quite
important to have since ip6 addr
So how can I create a function that it will choose, the option of
casting is not available to me
Dave
On Tue, 2004-01-06 at 19:47, Tom Lane wrote:
> Dave Cramer <[EMAIL PROTECTED]> writes:
> > I have a function expecting a timestamp, cstring, cstring
> > if I pass it a timestamp, unknown, unkown i
You are correct, it can't choose
Dave
On Tue, 2004-01-06 at 19:47, Tom Lane wrote:
> Dave Cramer <[EMAIL PROTECTED]> writes:
> > I have a function expecting a timestamp, cstring, cstring
> > if I pass it a timestamp, unknown, unkown it works?
> > if I pass it an unknown, unknown, unkown, it can't
So one of the client machines for one of my databases at work resides
on 10.128.0.45. I had to enter something in pg_hba.conf for it today,
as we're bringing this database up. We have a lot of 10/8 subnets, and
I use it at home, so I'm accustomed to just using 10.128.45 for the IP.
Strangely, howev
Dave Cramer <[EMAIL PROTECTED]> writes:
> I have a function expecting a timestamp, cstring, cstring
> if I pass it a timestamp, unknown, unkown it works?
> if I pass it an unknown, unknown, unkown, it can't be found?
You sure it's "can't find it" and not "can't choose among multiple
functions of t
How does the unknown data type get processed, there doesn't seem to be
any casts for it?
I have a function expecting a timestamp, cstring, cstring
if I pass it a timestamp, unknown, unkown it works?
if I pass it an unknown, unknown, unkown, it can't be found?
Dave
--
Dave Cramer
519 939 0336
IC
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 1. Make param_name equate to type_name (allowing IDENT or
>> unreserved_keyword), and move the following keywords from
>> "unreserved" to "col_name_keyword" status:
>> DOUBLE INOUT NATIONAL OUT
>>
>> 2. Make param_name equate to funct
Bruce Momjian wrote:
Andrew Dunstan wrote:
Bruce Momjian wrote:
Andrew Dunstan wrote:
I thought we had thrashed this out back in August. Certainly the only
thing I recall seeing after I submitted the patch was some stylistic
criticism from Neil, which I addressed in a revised pa
Jon Jensen wrote:
On Tue, 6 Jan 2004, Andrew Dunstan wrote:
Also, I would like to see some kind of session identifier that is more
unique than pid, which wraps around. Ideally we could have 10{pid},
then then the pid wraps around, 20{pid), or something like that.
This requires some t
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >Andrew Dunstan wrote:
> >
> >
> >>I thought we had thrashed this out back in August. Certainly the only
> >>thing I recall seeing after I submitted the patch was some stylistic
> >>criticism from Neil, which I addressed in a revised patch.
Am Tuesday 06 January 2004 21:30 schrieb Jon Jensen:
> On Tue, 6 Jan 2004, Andrew Dunstan wrote:
> > >Also, I would like to see some kind of session identifier that is more
> > >unique than pid, which wraps around. Ideally we could have 10{pid},
> > >then then the pid wraps around, 20{pid), or som
On Tue, 6 Jan 2004, Andrew Dunstan wrote:
> >Also, I would like to see some kind of session identifier that is more
> >unique than pid, which wraps around. Ideally we could have 10{pid},
> >then then the pid wraps around, 20{pid), or something like that.
>
> This requires some thought. ISTM it w
Tom Lane wrote:
I've been reviewing Dennis Bjorklund's patch to support named
function parameters:
http://archives.postgresql.org/pgsql-patches/2003-12/msg00176.php
One thing I didn't like about it was that the grammar declared
param_name as plain IDENT, meaning that you could not use even
"unre
Tom,
> I've made some progress on this over the last week or two. Would it be
> possible to retry that benchmark with CVS tip?
Yes! I'll just need some time to get my laptop set up for running it. My
server is, alas, in storage due to me being "between offices".
--
-Josh Berkus
Aglio Da
I've been reviewing Dennis Bjorklund's patch to support named
function parameters:
http://archives.postgresql.org/pgsql-patches/2003-12/msg00176.php
One thing I didn't like about it was that the grammar declared
param_name as plain IDENT, meaning that you could not use even
"unreserved" keywords a
Bruce Momjian wrote:
Andrew Dunstan wrote:
I thought we had thrashed this out back in August. Certainly the only
thing I recall seeing after I submitted the patch was some stylistic
criticism from Neil, which I addressed in a revised patch.
Anyway, it is in principle doable. That's partly why
(To hackers)
On Tue, Jan 06, 2004 at 01:06:17PM -0500, Neil Conway wrote:
> P.S. BTW, how does everyone feel about the methodology I've been using
> for submitting and applying patches? The procedure I'm following is:
The only thing I'd like is that the applied patch is attached in the
automatic
Andrew Dunstan wrote:
> Bruce Momjian said:
> > Andrew Dunstan wrote:
> >>
> >> 2 things.
> >>
> >> I submitted a patch for this 5 months ago, which is still waiting to
> be merged (hope it hasn't bitrotted in the meantime):
> >>
> >> . Allow log lines to include session-level information, like da
objectdefinition is defined as a record variable. It works fine when I remove the statement trying to get the dynamically concocted string executed and the results placed into the aliasvalue variable which is varchar.
My first question is, Can you perform a select on a variable? Such as in the c
A E <[EMAIL PROTECTED]> writes:
> I tried to use a for in loop to execute the statement to try to get some dynamic
> functionality but I get "ERROR: missing ".." at end of SQL expression" what am I
> doing wrong?
Did you declare the loop variable (here, "objectdefinition") as a
record or rowty
Tom and Chris,
I tried to use a for in loop to execute the statement to try to get some dynamic functionality but I get "ERROR: missing ".." at end of SQL _expression_" what am I doing wrong?
Code:
qry := ''select * from ''|| trim(realname) ||'' where ''|| trim(searchfield) ||'' like %'
> http://www.pgsql.ru/
> We are welcome your feedback and comments.
Very nice work!
I've just found some docs I was looking for a long time :)
Bye, Chris.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Bruce Momjian said:
> Andrew Dunstan wrote:
>>
>> 2 things.
>>
>> I submitted a patch for this 5 months ago, which is still waiting to
be merged (hope it hasn't bitrotted in the meantime):
>>
>> . Allow log lines to include session-level information, like database
and user
>>
>> If nobody is worki
Am Sonntag, 4. Januar 2004 20:13 schrieb Alex J. Avriette:
> On Sat, Jan 03, 2004 at 08:25:21PM -0500, Bruce Momjian wrote:
> > > I finally figure it out, I just end up forgetting again later. I still
...
>
> /functions
> /databases
>
...
Long options sounds really good. It is like GNU-tools. A s
31 matches
Mail list logo