On Mon, 2008-07-14 at 22:54 -0400, Jonah H. Harris wrote:
> On Mon, Jul 14, 2008 at 9:18 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> > Kaare Rasmussen <[EMAIL PROTECTED]> writes:
> >> But yes, it has to be enabled, and yes it has to have a performance cost
> >> somehow, but people are requesting it,
Is there a COPY equivalent for updates?
eg I've
create table t1 (
id int primary key,
col1 int,
col2 int,
col3 varchar(32)
);
and a CSV file
10,4,5,"abc"
13,7,3,"def"
18,12,77,"ghi"
I'd like to
UPDATE t1 (col1, col2, col3) from file with @1 as primary key;
or
UPDATE t1 (col1, col2, col
Hai all,
Thanks to all , I got the answer, actualy I am write the function in
openoffice.org and paste it to a .sql file that is the reason for the error.
thanks
Anoop
On Mon, Jul 14, 2008 at 7:32 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Anoop G" <[EMAIL PROTECTED]> writes:
> > ERRO
On Mon, Jul 14, 2008 at 9:18 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Kaare Rasmussen <[EMAIL PROTECTED]> writes:
>> But yes, it has to be enabled, and yes it has to have a performance cost
>> somehow, but people are requesting it, and somehow I don't think Oracle
>> developed the feature just for
Kaare Rasmussen <[EMAIL PROTECTED]> writes:
> But yes, it has to be enabled, and yes it has to have a performance cost
> somehow, but people are requesting it, and somehow I don't think Oracle
> developed the feature just for fun.
No, they developed it for marketing.
Keep in mind that Oracle ha
On Mon, 2008-07-14 at 22:38 +0200, Kaare Rasmussen wrote:
> > This sounds a lot like the functionality that a temporal data model
> > would give you. In this model you never delete tuples from your
> > database, your only insert and update tuples that are valid for
> > specific periods of time.
>
Lewis Cunningham wrote:
> --- On Mon, 7/14/08, Kaare Rasmussen <[EMAIL PROTECTED]> wrote:
>
> > But yes, it has to be enabled, and yes it has to have a
> > performance cost
> > somehow, but people are requesting it, and somehow I
>
> AFAIK, It is built from undo so there is no ADDITIONAL overhea
--- On Mon, 7/14/08, Kaare Rasmussen <[EMAIL PROTECTED]> wrote:
> But yes, it has to be enabled, and yes it has to have a
> performance cost
> somehow, but people are requesting it, and somehow I
AFAIK, It is built from undo so there is no ADDITIONAL overhead. It just saves
the undo that is cr
On Mon, Jul 14, 2008 at 1:38 PM, Kaare Rasmussen <[EMAIL PROTECTED]> wrote:
> Isn't this exactly what Alvaro describes? The time travel feature that was
> removed because it made Postgres too slow to use in production?
No, I imagine that time travel was built into the Postgresql
architecture and w
> This sounds a lot like the functionality that a temporal data model
> would give you. In this model you never delete tuples from your
> database, your only insert and update tuples that are valid for
> specific periods of time.
Isn't this exactly what Alvaro describes? The time travel feature t
> which "it would come in handy" wouldn't have enabled it. (FWIW this
> feature used to exist in the Berkeley code, under the cool name "time
> travel", and was removed a long time ago.)
No, it didn't AFAIK. Timetravel kept all tuples in the database with all
indexes and constraints active at al
On Mon, 2008-07-14 at 21:59 +0200, Kaare Rasmussen wrote:
> > I just lost a months worth of stats data myself, so join the club. It
> > wasn't critical data, but it would have been nice to have kept
> > around...
>
> I also think there could be a TODO item in it. If vacuum instead of removing
>
Kaare Rasmussen escribió:
> I don't say it's an important feature, but it would come in handy for people
> who really really need it. And perhaps a developer wouldn't mind scratching
> this itch some time in the future.
It would need to be enabled beforehand, and most people I've seen for
which
On Mon, Jul 14, 2008 at 12:59 PM, Kaare Rasmussen <[EMAIL PROTECTED]> wrote:
> I also think there could be a TODO item in it. If vacuum instead of removing
> items, somehow stashed them away in a storage limited archive it would be
> possible to do a SELECT...AS OF TIMESTAMP.
This sounds a lot lik
> I just lost a months worth of stats data myself, so join the club. It
> wasn't critical data, but it would have been nice to have kept
> around...
I also think there could be a TODO item in it. If vacuum instead of removing
items, somehow stashed them away in a storage limited archive it would
On Mon, Jul 14, 2008 at 9:20 AM, samantha mahindrakar
<[EMAIL PROTECTED]> wrote:
> I didnt no the thread would become a postgresVSoracle thing. I just lost
> couple of thousand rows and could not retrieve them back, so i wanted to
> know if postgres had some way to get it back. Iam just a few days
I didnt no the thread would become a postgresVSoracle thing. I just lost
couple of thousand rows and could not retrieve them back, so i wanted to
know if postgres had some way to get it back. Iam just a few days
expereinced in postgres hence iam still discovering its features.
No intention of compa
"Anoop G" <[EMAIL PROTECTED]> writes:
> ERROR: syntax error at or near "\226" at character 18
> QUERY: SELECT mf,sf,(mf \226 mf * comm /100) \226 (sf \226 sf * comm/100) as
> flt_claim
> CONTEXT: PL/pgSQL function "test_perc" line 7 at for over execute statement
> LINE 1: SELECT mf,sf,(mf \226 m
Hi,
Anoop G wrote:
vchr_query:= 'SELECT mf,sf,(mf – mf * comm /100) – (sf – sf * comm/100)
as flt_claim';
Simply use a real minus sign '-', and not a hyphen '–'. (Try
copy'n'pasting from this email, if nothing else works ;-) )
Regards
Markus
--
Sent via pgsql-sql mailing list (pgsql-sql@
19 matches
Mail list logo
