hi,
I want to make the following thing :
select-based updatable VIEW, which have two more virtual-fields.
One of them is concatenation of others and the second is calculated on the fly.
Can I do this and if yes how? can u give some example?
Here is the test bed :
table1) id, date, field1, field2
table2) id, fieldA, fieldB, fkID
now I want to make a view that is
create view as select
t1.id, t1.date, t1.field1, t1.field2,
t2.fieldA, t2.fieldB,
state, stuff
from table1 as t1, table2 as t2
where t1.id = t2.fkID WHERE "state" is caluclated like this :
state = 'red' if date > today
state = 'green' if date < today
state = 'blue' unless date
AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
can this be done, if yes how.
tia
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org 20 1971
hi, ra****@tvskat.net wrote: create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date
AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
can this be done, if yes how.
try with case:
case when date > current_timestamp then 'red' when date <
current_timestamp then 'green' else 'blue' end as state,
t1.field2||t2.fieldA as stuff
C.
hi, ra****@tvskat.net wrote: create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date
AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
can this be done, if yes how.
try with case:
case when date > current_timestamp then 'red' when date <
current_timestamp then 'green' else 'blue' end as state,
t1.field2||t2.fieldA as stuff
C. ra****@tvskat.net wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
Here is the test bed :
table1) id, date, field1, field2 table2) id, fieldA, fieldB, fkID
now I want to make a view that is
create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
SELECT ...
CASE
WHEN date < CURRENT_DATE THEN 'green'::text
WHEN date > CURRENT_DATE THEN 'red'::text
ELSE 'blue'::text
END
AS state,
(t1.field2 || t2.fieldA) AS stuff
FROM ... BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable,
you'll need to write your own rules (see manuals for details).
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html ra****@tvskat.net wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
Here is the test bed :
table1) id, date, field1, field2 table2) id, fieldA, fieldB, fkID
now I want to make a view that is
create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
SELECT ...
CASE
WHEN date < CURRENT_DATE THEN 'green'::text
WHEN date > CURRENT_DATE THEN 'red'::text
ELSE 'blue'::text
END
AS state,
(t1.field2 || t2.fieldA) AS stuff
FROM ... BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable,
you'll need to write your own rules (see manuals for details).
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
NOTE THAT if field2 or fieldA might contain NULL values u should use
coalesce if u don't want to have a NULL value if one of the fields is NULL:
If field2 and fieldA are strings you will have something like that
(coalesce(t1.field2,'') ||coalesce(t2.fieldA,'')) AS stuff ra****@tvskat.net wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
Here is the test bed :
table1) id, date, field1, field2 table2) id, fieldA, fieldB, fkID
now I want to make a view that is
create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date
AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
SELECT ... CASE WHEN date < CURRENT_DATE THEN 'green'::text WHEN date > CURRENT_DATE THEN 'red'::text ELSE 'blue'::text END AS state, (t1.field2 || t2.fieldA) AS stuff FROM ...
BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable, you'll need to write your own rules (see manuals for details).
-- Richard Huxton Archonet Ltd
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
NOTE THAT if field2 or fieldA might contain NULL values u should use
coalesce if u don't want to have a NULL value if one of the fields is NULL:
If field2 and fieldA are strings you will have something like that
(coalesce(t1.field2,'') ||coalesce(t2.fieldA,'')) AS stuff ra****@tvskat.net wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
Here is the test bed :
table1) id, date, field1, field2 table2) id, fieldA, fieldB, fkID
now I want to make a view that is
create view as select t1.id, t1.date, t1.field1, t1.field2, t2.fieldA, t2.fieldB, state, stuff from table1 as t1, table2 as t2 where t1.id = t2.fkID
WHERE "state" is caluclated like this :
state = 'red' if date > today state = 'green' if date < today state = 'blue' unless date
AND 'stuff' is concatenation of t1.field2 and t2.fieldA.
SELECT ... CASE WHEN date < CURRENT_DATE THEN 'green'::text WHEN date > CURRENT_DATE THEN 'red'::text ELSE 'blue'::text END AS state, (t1.field2 || t2.fieldA) AS stuff FROM ...
BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable, you'll need to write your own rules (see manuals for details).
-- Richard Huxton Archonet Ltd
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
> SELECT ... CASE WHEN date < CURRENT_DATE THEN 'green'::text WHEN date > CURRENT_DATE THEN 'red'::text ELSE 'blue'::text END AS state, (t1.field2 || t2.fieldA) AS stuff FROM ...
]- aha thanx.. BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable, you'll need to write your own rules (see manuals for details).
]- yep, i have to write RULES how updates/inserts will be propagandated( i made a quick read
of this section from the docs..)
-- Richard Huxton Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
> SELECT ... CASE WHEN date < CURRENT_DATE THEN 'green'::text WHEN date > CURRENT_DATE THEN 'red'::text ELSE 'blue'::text END AS state, (t1.field2 || t2.fieldA) AS stuff FROM ...
]- aha thanx.. BOTH state and stuff will be only available for SELECTs on the view i.e. they are not updatable ..
All views in PG are read-only. If you want to make the view updatable, you'll need to write your own rules (see manuals for details).
]- yep, i have to write RULES how updates/inserts will be propagandated( i made a quick read
of this section from the docs..)
-- Richard Huxton Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
On Fri, Jun 18, 2004 at 16:13:38 +0300,
"ra****@tvskat.net" <ra****@tvskat.net> wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
You can do this using the rule system.
Below is a dump of a test of an updatable view definition that I made with
playing with this. I don't have the original source script. The pg_dump
output is a bit verbose with constraint definitions, but it should be fine
for showing you how to make simple updatable views.
CREATE TABLE test1 (
id serial NOT NULL,
name text NOT NULL
);
CREATE TABLE test2 (
id serial NOT NULL,
name text NOT NULL
);
CREATE TABLE test3 (
id1 integer NOT NULL,
id2 integer NOT NULL
);
CREATE VIEW test4 AS
SELECT test1.name AS name1, test2.name AS name2 FROM test1, test2, test3 WHERE ((test1.id = test3.id1) AND (test2.id = test3.id2));
ALTER TABLE ONLY test1
ADD CONSTRAINT test1_name_key UNIQUE (name);
ALTER TABLE ONLY test2
ADD CONSTRAINT test2_pkey PRIMARY KEY (id);
ALTER TABLE ONLY test2
ADD CONSTRAINT test2_name_key UNIQUE (name);
ALTER TABLE ONLY test3
ADD CONSTRAINT test3_pkey PRIMARY KEY (id1, id2);
ALTER TABLE ONLY test3
ADD CONSTRAINT "$1" FOREIGN KEY (id1) REFERENCES test1(id);
ALTER TABLE ONLY test3
ADD CONSTRAINT "$2" FOREIGN KEY (id2) REFERENCES test2(id);
CREATE RULE test4_ins AS ON INSERT TO test4 DO INSTEAD INSERT INTO test3 (id1, id2) SELECT test1.id, test2.id FROM test1, test2 WHERE ((test1.name = new.name1) AND (test2.name = new.name2));
CREATE RULE test4_del AS ON DELETE TO test4 DO INSTEAD DELETE FROM test3 WHERE ((((test1.name = old.name1) AND (test2.name = old.name2)) AND (test1.id = test3.id1)) AND (test2.id = test3.id2));
CREATE RULE test4_upd AS ON UPDATE TO test4 DO INSTEAD UPDATE test3 SET id1 = a1.id, id2 = a2.id FROM test1 a1, test2 a2, test1 b1, test2 b2 WHERE ((((((a1.name = new.name1) AND (a2.name = new.name2)) AND (test3.id1 = b1.id)) AND (test3.id2 = b2.id)) AND (b1.name = old.name1)) AND (b2.name = old.name2));
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
On Fri, Jun 18, 2004 at 16:13:38 +0300,
"ra****@tvskat.net" <ra****@tvskat.net> wrote: hi,
I want to make the following thing : select-based updatable VIEW, which have two more virtual-fields. One of them is concatenation of others and the second is calculated on the fly. Can I do this and if yes how? can u give some example?
You can do this using the rule system.
Below is a dump of a test of an updatable view definition that I made with
playing with this. I don't have the original source script. The pg_dump
output is a bit verbose with constraint definitions, but it should be fine
for showing you how to make simple updatable views.
CREATE TABLE test1 (
id serial NOT NULL,
name text NOT NULL
);
CREATE TABLE test2 (
id serial NOT NULL,
name text NOT NULL
);
CREATE TABLE test3 (
id1 integer NOT NULL,
id2 integer NOT NULL
);
CREATE VIEW test4 AS
SELECT test1.name AS name1, test2.name AS name2 FROM test1, test2, test3 WHERE ((test1.id = test3.id1) AND (test2.id = test3.id2));
ALTER TABLE ONLY test1
ADD CONSTRAINT test1_name_key UNIQUE (name);
ALTER TABLE ONLY test2
ADD CONSTRAINT test2_pkey PRIMARY KEY (id);
ALTER TABLE ONLY test2
ADD CONSTRAINT test2_name_key UNIQUE (name);
ALTER TABLE ONLY test3
ADD CONSTRAINT test3_pkey PRIMARY KEY (id1, id2);
ALTER TABLE ONLY test3
ADD CONSTRAINT "$1" FOREIGN KEY (id1) REFERENCES test1(id);
ALTER TABLE ONLY test3
ADD CONSTRAINT "$2" FOREIGN KEY (id2) REFERENCES test2(id);
CREATE RULE test4_ins AS ON INSERT TO test4 DO INSTEAD INSERT INTO test3 (id1, id2) SELECT test1.id, test2.id FROM test1, test2 WHERE ((test1.name = new.name1) AND (test2.name = new.name2));
CREATE RULE test4_del AS ON DELETE TO test4 DO INSTEAD DELETE FROM test3 WHERE ((((test1.name = old.name1) AND (test2.name = old.name2)) AND (test1.id = test3.id1)) AND (test2.id = test3.id2));
CREATE RULE test4_upd AS ON UPDATE TO test4 DO INSTEAD UPDATE test3 SET id1 = a1.id, id2 = a2.id FROM test1 a1, test2 a2, test1 b1, test2 b2 WHERE ((((((a1.name = new.name1) AND (a2.name = new.name2)) AND (test3.id1 = b1.id)) AND (test3.id2 = b2.id)) AND (b1.name = old.name1)) AND (b2.name = old.name2));
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
Hi
One of our production systems was running 7.4.1 for a few months, when
suddenly some queries that used a specifiy table (a cache table) started
crashing the backend.
A colleague of mine "fixed" the problem by simply dumping and rebuilding
the affected table (That was possible since it was only a cache for the
results of slow queries).
About 2 weeks later, the problem reappeared - this time affecting more
tables. It started to analyze the problem, and found out about the
alignment-bug in 7.4.1. I upgraded to 7.4.2, and fixed the system-tables
according to the 7.4.2 release-note. But this didn't really help - the
"analyze table" issued after fixing the system-tables exited with an
error about an invalid page header in one of our tables. Dumping the
database was also impossible at that stage - some tables would cause pg_dump
to either abort, or to silently block (we had it running for about 10
minutes, and it didn't output a single line in that time).
I finally fixed the problem by dumping all relevant tables "by hand", and
restoring them into a clean install of 7.4.2.
Since that 7.4.2 release-note only talked about crashing queries due to the
7.4.1 bug, but not about data-corruption occuring, I wondered if the
symptoms I have seen are related to the alignment bug in 7.4.1 or not.
The affected tables where all updates very frequently, and were quite large
(about a million records each). The data is comes from daily imports, which
delete the old records, and insert the new ones inside a transaction.
I a backup of the corrupted postgres-data, so I could do further analysis
if necessary.
greetings, Florian Pflug
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
Hi
One of our production systems was running 7.4.1 for a few months, when
suddenly some queries that used a specifiy table (a cache table) started
crashing the backend.
A colleague of mine "fixed" the problem by simply dumping and rebuilding
the affected table (That was possible since it was only a cache for the
results of slow queries).
About 2 weeks later, the problem reappeared - this time affecting more
tables. It started to analyze the problem, and found out about the
alignment-bug in 7.4.1. I upgraded to 7.4.2, and fixed the system-tables
according to the 7.4.2 release-note. But this didn't really help - the
"analyze table" issued after fixing the system-tables exited with an
error about an invalid page header in one of our tables. Dumping the
database was also impossible at that stage - some tables would cause pg_dump
to either abort, or to silently block (we had it running for about 10
minutes, and it didn't output a single line in that time).
I finally fixed the problem by dumping all relevant tables "by hand", and
restoring them into a clean install of 7.4.2.
Since that 7.4.2 release-note only talked about crashing queries due to the
7.4.1 bug, but not about data-corruption occuring, I wondered if the
symptoms I have seen are related to the alignment bug in 7.4.1 or not.
The affected tables where all updates very frequently, and were quite large
(about a million records each). The data is comes from daily imports, which
delete the old records, and insert the new ones inside a transaction.
I a backup of the corrupted postgres-data, so I could do further analysis
if necessary.
greetings, Florian Pflug
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
"Florian G. Pflug" <fg*@phlo.org> writes: ... I upgraded to 7.4.2, and fixed the system-tables according to the 7.4.2 release-note. But this didn't really help - the "analyze table" issued after fixing the system-tables exited with an error about an invalid page header in one of our tables. Dumping the database was also impossible at that stage - some tables would cause pg_dump to either abort, or to silently block (we had it running for about 10 minutes, and it didn't output a single line in that time).
Since that 7.4.2 release-note only talked about crashing queries due to the 7.4.1 bug, but not about data-corruption occuring, I wondered if the symptoms I have seen are related to the alignment bug in 7.4.1 or not.
No, I don't think so. The alignment bug could cause the planner to
crash while retrieving statistics about a table, but it would not have
any effect on fetching the data in a table. In particular I don't
believe it could have any effect at all on a COPY command, which is what
I think you are saying was failing?
I finally fixed the problem by dumping all relevant tables "by hand", and restoring them into a clean install of 7.4.2.
How exactly did you do the "by hand" dump?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)
"Florian G. Pflug" <fg*@phlo.org> writes: ... I upgraded to 7.4.2, and fixed the system-tables according to the 7.4.2 release-note. But this didn't really help - the "analyze table" issued after fixing the system-tables exited with an error about an invalid page header in one of our tables. Dumping the database was also impossible at that stage - some tables would cause pg_dump to either abort, or to silently block (we had it running for about 10 minutes, and it didn't output a single line in that time).
Since that 7.4.2 release-note only talked about crashing queries due to the 7.4.1 bug, but not about data-corruption occuring, I wondered if the symptoms I have seen are related to the alignment bug in 7.4.1 or not.
No, I don't think so. The alignment bug could cause the planner to
crash while retrieving statistics about a table, but it would not have
any effect on fetching the data in a table. In particular I don't
believe it could have any effect at all on a COPY command, which is what
I think you are saying was failing?
I finally fixed the problem by dumping all relevant tables "by hand", and restoring them into a clean install of 7.4.2.
How exactly did you do the "by hand" dump?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)
> view i.e. they are not updatable ..
|>
|> All views in PG are read-only. If you want to make the view updatable,
|> you'll need to write your own rules (see manuals for details).
|
|]- yep, i have to write RULES how updates/inserts will be propagandated( i made a quick read
|of this section from the docs..)
]- re: to myself... In fact I was using postgres in the past afaik 6.x versions or so (no outer joins, rule system was still not fully working ... it was good on paper was good but, ... now glad it has advanced so much :"))..
then i got using Inter Base(FireBird). (really cool db :") )
From what I see 7.x series has made huge step forward.. probably now surpacing firebird on features side.. (they had hard time
adapting Interbase code)
(no flame pls!)
AFAIK firebird(interbase) and postgres are the only DB with multiversioning engines, is that true ?
thanx again for your help..
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org
> view i.e. they are not updatable ..
|>
|> All views in PG are read-only. If you want to make the view updatable,
|> you'll need to write your own rules (see manuals for details).
|
|]- yep, i have to write RULES how updates/inserts will be propagandated( i made a quick read
|of this section from the docs..)
]- re: to myself... In fact I was using postgres in the past afaik 6.x versions or so (no outer joins, rule system was still not fully working ... it was good on paper was good but, ... now glad it has advanced so much :"))..
then i got using Inter Base(FireBird). (really cool db :") )
From what I see 7.x series has made huge step forward.. probably now surpacing firebird on features side.. (they had hard time
adapting Interbase code)
(no flame pls!)
AFAIK firebird(interbase) and postgres are the only DB with multiversioning engines, is that true ?
thanx again for your help..
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org
On Fri, Jun 18, 2004 at 02:32:16PM -0400, Tom Lane wrote: Since that 7.4.2 release-note only talked about crashing queries due to the 7.4.1 bug, but not about data-corruption occuring, I wondered if the symptoms I have seen are related to the alignment bug in 7.4.1 or not.
No, I don't think so. The alignment bug could cause the planner to crash while retrieving statistics about a table, but it would not have any effect on fetching the data in a table. In particular I don't believe it could have any effect at all on a COPY command, which is what I think you are saying was failing?
Yes - but also selects on the broken tables where failing (causing the
backend to crash) - that's how we noticed to problem in the first place. I finally fixed the problem by dumping all relevant tables "by hand", and restoring them into a clean install of 7.4.2.
How exactly did you do the "by hand" dump?
"by hand" was a rather stupid explaination ;-) I used the regular pg_dump
app, but I dumped only the tables which contain valueable data, not the ones
which could be recreated from files outside of the database. Luckily all the
important tables could still be dumped.
greetings, Florian Pflug
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
raptor wrote: ]- re: to myself... In fact I was using postgres in the past afaik 6.x versions or so (no outer joins, rule system was still not fully working ... it was good on paper was good but, ... now glad it has advanced so much :")).. then i got using Inter Base(FireBird). (really cool db :") ) From what I see 7.x series has made huge step forward.. probably now surpacing firebird on features side.. (they had hard time adapting Interbase code) (no flame pls!)
Firebird is the only viable open-source alternative to PG that I can
think of (which has been a viable project for any length of time).
AFAIK firebird(interbase) and postgres are the only DB with multiversioning engines, is that true ?
I think Oracle has its version.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
On Mon, 2004-06-21 at 13:34, Richard Huxton wrote: raptor wrote: ]- re: to myself... In fact I was using postgres in the past afaik 6.x versions or so (no outer joins, rule system was still not fully working ... it was good on paper was good but, ... now glad it has advanced so much :")).. then i got using Inter Base(FireBird). (really cool db :") ) From what I see 7.x series has made huge step forward.. probably now surpacing firebird on features side.. (they had hard time adapting Interbase code) (no flame pls!)
Firebird is the only viable open-source alternative to PG that I can think of (which has been a viable project for any length of time).
AFAIK firebird(interbase) and postgres are the only DB with multiversioning engines, is that true ?
I think Oracle has its version.
According to the author of them, innodb tables under MySQL use MVCC as
well. Now if someone could just fix the parser in MySQL to not be
broken...
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)
Richard Huxton wrote: raptor wrote: AFAIK firebird(interbase) and postgres are the only DB with multiversioning engines, is that true ?
I think Oracle has its version.
Yes, Oracle has it. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Neil |
last post by:
I've been discussing here a SQL 7 view which scrolls slowly when linked to
an Access 2000 MDB. After trying various things, I've distilled it down to
the following: when the linked view has a...
|
by: Adrian Herscu |
last post by:
Hi all,
In which circumstances it is appropriate to declare methods as non-virtual?
Thanx,
Adrian.
|
by: Brian Henry |
last post by:
Here is another virtual mode example for the .NET 2.0 framework while
working with the list view. Since you can not access the items collection of
the list view you need to do sorting another...
|
by: raptor |
last post by:
hi,
I want to make the following thing :
select-based updatable VIEW, which have two more virtual-fields.
One of them is concatenation of others and the second is calculated on the fly.
Can I...
|
by: antonyliu2002 |
last post by:
I've set up the virtual smtp server on my IIS 5.1 like so:
1. Assign IP address to "All Unassigned", and listen to port 25.
2. Access Connection granted to "127.0.0.1".
3. Relay only allow...
|
by: Jess |
last post by:
Hello,
If I have a class that has virtual but non-pure declarations, like
class A{
virtual void f();
};
Then is A still an abstract class? Do I have to have "virtual void
f() = 0;"...
|
by: Ken Fine |
last post by:
Hi, hoping someone can help out with what's a simple question.
I am using the ASP.NET VE map control here on a site, which I am still
developing. I'm putting picture icons on a map:
...
|
by: akshaycjoshi |
last post by:
I am reading a book which says
Even though unboxed value types don't have a type object pointer, you can still call virtual
methods (such as Equals, GetHashCode, or ToString) inherited or...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| |