On Feb 9, 2008 4:58 PM, Jan Wieck <[EMAIL PROTECTED]> wrote:
> I wonder if the efforts to provide mirrors for many different systems can
> hurt later down the road. It is pretty obvious that amost every current
> system has options to convert from or to mirror a CVS repository. But what if
> we
Hi.
From: "Tom Lane" <[EMAIL PROTECTED]>
A possibly bigger problem is that the solution for postfix ops doesn't
scale nicely: we'd have to list not only IDENT, but *every* can-be-ColId
keyword, in the %precedence list, which (a) is a maintenance headache,
(b) causes a conflict because some are
On Sat, 9 Feb 2008, Jan Wieck wrote:
It is pretty obvious that amost every current system has options to
convert from or to mirror a CVS repository. But what if we someday
really want to use something else as the master repository?
In order to export from CVS into one of the newer systems, th
On Feb 10, 2008 8:58 AM, Jan Wieck <[EMAIL PROTECTED]> wrote:
> I wonder if the efforts to provide mirrors for many different systems can
> hurt later down the road. It is pretty obvious that amost every current
> system has options to convert from or to mirror a CVS repository. But what if
> we
Gregory Stark <[EMAIL PROTECTED]> writes:
> There are other rules that have a %prec on the rule itself, does that not work
> here? *off to read the fine manual now*
No, the decision is driven by comparing the precedence of the rule to
that of the input token, so you need precedences on both to res
I wonder if the efforts to provide mirrors for many different systems can hurt
later down the road. It is pretty obvious that amost every current system has
options to convert from or to mirror a CVS repository. But what if we someday
really want to use something else as the master repository? A
"Tom Lane" <[EMAIL PROTECTED]> writes:
> A possibly bigger problem is that the solution for postfix ops doesn't
> scale nicely: we'd have to list not only IDENT, but *every* can-be-ColId
> keyword, in the %precedence list, which (a) is a maintenance headache,
> (b) causes a conflict because some a
Gregory Stark <[EMAIL PROTECTED]> writes:
> Of course it would still be better if we could get it closer to ColId. YEAR
> MONTH DAY HOUR MINUTE SECOND the only problem spots? How much else had to
> change to work around other conflicts?
No, to make it ColId we'd also have to reserve all of these:
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Sure, just like a + + b is ambiguous. We define an arbitrary choice and tell
>> people to put parentheses if they want the other. It's not too hard to write
>> SELECT (a +) b, ...
>> if you want an alias. Besides
Gregory Stark <[EMAIL PROTECTED]> writes:
> Sure, just like a + + b is ambiguous. We define an arbitrary choice and tell
> people to put parentheses if they want the other. It's not too hard to write
> SELECT (a +) b, ...
> if you want an alias. Besides, nobody uses postfix expressions anyways. It
Gregory Stark wrote:
"Stefan Kaltenbrunner" <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
Not sure if this is platform-specific, but I keep being annoyed by not being
able to actually *view* the patches in the queue. I have to download them,
and then
"Stefan Kaltenbrunner" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Magnus Hagander <[EMAIL PROTECTED]> writes:
>>> Not sure if this is platform-specific, but I keep being annoyed by not being
>>> able to actually *view* the patches in the queue. I have to download them,
>>> and then open them
Tom Lane wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
Not sure if this is platform-specific, but I keep being annoyed by not
being able to actually *view* the patches in the queue. I have to
download them, and then open them separately. I can't just view them in
the browser, because they
On Sat, Feb 09, 2008 at 12:29:10PM -0500, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > I am surprised to see
>
> > NOTICE: (1,two,"Sat 09 Feb 16:47:44.514503 2008")
>
> This is the expected formatting for a composite type. Read
> http://www.postgresql.org/docs/8.3/static/row
Patrick Welche <[EMAIL PROTECTED]> writes:
> I am surprised to see
> NOTICE: (1,two,"Sat 09 Feb 16:47:44.514503 2008")
This is the expected formatting for a composite type. Read
http://www.postgresql.org/docs/8.3/static/rowtypes.html#AEN6266
regards, tom lane
-
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Not sure if this is platform-specific, but I keep being annoyed by not
> being able to actually *view* the patches in the queue. I have to
> download them, and then open them separately. I can't just view them in
> the browser, because they're all na
On Feb 10, 2008 3:50 AM, Patrick Welche <[EMAIL PROTECTED]> wrote:
> NOTICE: (1,two,"Sat 09 Feb 16:47:44.514503 2008")
> INSERT 0 0
>
I think what you're seeing is the syntax for row literals.
You can get an idea of how it looks without having to write trigger
functions, e.g.:
> select row(1, '
Given the following trivial trigger example:
-- create language plpgsql;
create table foo (a integer, b text, c timestamp);
create function foo_insert() returns trigger as $$
begin
raise notice '%', new;
return null;
end;
$$ language plpgsql;
create trigger foo_ins bef
Andrew Dunstan escribió:
>
> Joshua D. Drake wrote:
Can you document what you actually do on the developers' wiki?
>>> I'd prefer we do not advertise it until it's actually usable.
>>
>> Wait, what are we talking about? The SVN mirror we have right now is
>> perfectly usable.
Bruce Momjian wrote:
IMHO an mbox is not the right interface either, though. I guess there
must be something in the middle, like a *cough*patch manager*cough*. At
least there should be a way to mark patches: a "is this a patch" (or
merely discussion) boolean; and a free-form field where other p
Hi
After Tom Lane did patch for copyfuncs.c my problem is gone !
Thanks Tom
Best regards,
Vladimir Kokovic, DP senior, Belgrade, Serbia
---(end of broadcast)---
TIP 6: explain analyze is your friend
Joshua D. Drake wrote:
Can you document what you actually do on the developers' wiki?
I'd prefer we do not advertise it until it's actually usable.
Wait, what are we talking about? The SVN mirror we have right now is
perfectly usable. It just has to be rebuilt a couple of time
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> But yeah, c_expr isn't enough. We really need {a,b}_expr sans postfix
>> expressions.
>
> How's that going to help? As long as postfix operators exist at all,
>
> SELECT a + b, ...
>
> is going to be ambig
Joshua D. Drake wrote:
On Fri, 8 Feb 2008 12:39:36 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Andrew Dunstan escribió:
Alvaro Herrera wrote:
Florian Pflug escribió:
Yeah, the SVN mirror in commandprompt.com is recreated from scratch
every time. This sucks, we know -- I think it's on Jo
On Fri, 8 Feb 2008 12:39:36 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Andrew Dunstan escribió:
>
> > Alvaro Herrera wrote:
> >> Florian Pflug escribió:
>
> >> Yeah, the SVN mirror in commandprompt.com is recreated from scratch
> >> every time. This sucks, we know -- I think it's on Josh
25 matches
Mail list logo
