On 10/14/06, Jan Cruz [EMAIL PROTECTED] wrote:
Thank you...I supposed I'll try this one if it could suits my needs.It's really hard to maintain views and functions updates.I have downloaded and read the instruction for pgdiff but I am not familiar with aol_server and it's kinda troublesome
Thank you...I supposed I'll try this one if it could suits my needs.It's really hard to maintain views and functions updates.On 10/11/06, A. Kretschmer
[EMAIL PROTECTED] wrote:
amWed, dem 11.10.2006, um7:37:11 -0300 mailte Jorge Godoy folgendes: Jan Cruz [EMAIL PROTECTED] writes
Is there a utility that could update/merge functions/views from a postgresql dump to an existing db?
As for deleting all but one row in a duplicated group, you're going tohave to get at them by the oid or ctid columns perhaps.
The other idea is to run CREATE TABLE newtable AS SELECT DISTINCT * FROMoldtable;.
I believe getting oid and/or ctid is not possible since it would not display/get
On 2/19/06, Michael Fuhr [EMAIL PROTECTED] wrote:
On Sat, Feb 18, 2006 at 04:48:55PM +0800, Jan Cruz wrote:
CREATE TABLE foo (id integer, t text);INSERT INTO foo VALUES (1, 'one');
INSERT INTO foo VALUES (2, 'two');
Thanks for the correct syntaxing Mike.
BTW I also got something like
When restoring a dump from sql_ascii encoding to latin9/utf8
the THIS STRING| result to THIS STRINGŠ thus it aborted the restore.
When I tried to dump a latin9/utf8 and restore it with the same encoding
having same string it goes well but it took a very long time to copy all data.
(1.6gb dump for
Note:
Assumption tables are already created and/or in existence.
I dump all data from a 7.3.5 db using LATIN9 encoding.
When I restore it back to a 8.1.3 db using LATIN9 encoding
it is much slower than restoring back to a 7.3.xx db.
Restoration from 7.3.5 to 8.1.3 took more or less 24 hours
I believe PostgreSQL treat UTF-8 and LATIN9 Differently.
When I tried to dump a db to a UTF-8 encoding and restore it
with UTF-8 encoding (also) it encountered problems with fields
that have unicoded values thus it stop from restoring the whole dump.
So I tried using LATIN9 encoding for both dump
Correct me if I am wrong but SQL procedural language doesn't have support for variable declarations?
And
Why does my stored function returns only the first row of the query instead of the whole set of query?
Kindly educate me :)
Why does my stored function returns only the first row of the query instead
of the whole set of query?Did you declare your function to return setof whatever ?I did but I don't know if I have to iterate/loop and use return next setof_foo
or just use return next as it is.
10 matches
Mail list logo
