Re: [GENERAL] Constraint Trigger's referenced_table

2007-12-23 Thread Richard Broersma Jr
--- On Sat, 12/22/07, Tom Lane [EMAIL PROTECTED] wrote: No, the purpose is to support foreign-key triggers. FK constraints are implemented via cooperating triggers on the two tables, and each trigger has to be able to look at the other table. When you say each trigger has to be able to look

Re: [GENERAL] update pg question?

2007-12-23 Thread Martijn van Oosterhout
On Thu, Dec 20, 2007 at 11:48:08PM -0800, ivan.hou wrote: how to update the pg version 8.1.3 to 8.1.10? should i backup and drop my database , or delete the /usr/local/pgsql directory? Just install it. Upgrades involving only the third number (the minor revision) don't require any changes to

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread Trevor Talbot
On 12/20/07, Martijn van Oosterhout [EMAIL PROTECTED] wrote: On Tue, Dec 18, 2007 at 02:53:16PM +0800, bookman bookman wrote: I know that every line of utf8 files is started with fffe or feff and ended with \r\n in windows but not in linux,so the character 1 has a space before it in the

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread Martin Gainty
it seems the use of BOM in UTF-8 is discouraged http://unicode.org/faq/utf_bom.html#BOM FF FE is UTF16-Little Endian FE FF is UTF16-Big Endian Please verify- Bedankt/ Martin- - Original Message - From: Trevor Talbot [EMAIL PROTECTED] To: pgsql-general@postgresql.org Sent: Sunday, December

Re: [GENERAL] postgres UTC different from perl?

2007-12-23 Thread Louis-David Mitterrand
On Wed, Dec 19, 2007 at 08:14:17PM -0500, Tom Lane wrote: Richard Huxton [EMAIL PROTECTED] writes: I'm not sure that (CURRENT_DATE AT TIME ZONE 'UTC') does what you think it does. Try setting your timezone to various offsets and exploring. In fact, I think it's adjusting in exactly the

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread brian
bookman bookman wrote: H i, I copied a table in sqlserver2005 to a txt file(There were many chinese words in it).I saved it as a file encoded by ANSI,but I cant open it in ubuntu.I tried GBK,GB18030, UTF8,It just could not be opened. Then I save it in windows with encoding UTF8,then I can

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread Trevor Talbot
On 12/23/07, Martin Gainty [EMAIL PROTECTED] wrote: it seems the use of BOM in UTF-8 is discouraged http://unicode.org/faq/utf_bom.html#BOM Where do you see it being discouraged? ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [GENERAL] postgres UTC different from perl?

2007-12-23 Thread Tom Lane
Louis-David Mitterrand [EMAIL PROTECTED] writes: On Wed, Dec 19, 2007 at 08:14:17PM -0500, Tom Lane wrote: Richard Huxton [EMAIL PROTECTED] writes: I'm not sure that (CURRENT_DATE AT TIME ZONE 'UTC') does what you think it does. Try setting your timezone to various offsets and exploring.

Re: [GENERAL] Constraint Trigger's referenced_table

2007-12-23 Thread Tom Lane
Richard Broersma Jr [EMAIL PROTECTED] writes: --- On Sat, 12/22/07, Tom Lane [EMAIL PROTECTED] wrote: No, the purpose is to support foreign-key triggers. FK constraints are implemented via cooperating triggers on the two tables, and each trigger has to be able to look at the other table.

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread Martin Gainty
the specifics.. Some byte oriented protocols expect ASCII characters at the beginning of a file. If UTF-8 is used with these protocols, use of the BOM as encoding form signature should be avoided. M-- - Original Message - From: Trevor Talbot [EMAIL PROTECTED] To:

Re: [GENERAL] pgsql cannot read utf8 files moved from windows correctly!

2007-12-23 Thread Trevor Talbot
On 12/23/00, Martin Gainty [EMAIL PROTECTED] wrote: the specifics.. Some byte oriented protocols expect ASCII characters at the beginning of a file. If UTF-8 is used with these protocols, use of the BOM as encoding form signature should be avoided. Sure, but that isn't true of generic text

Re: [GENERAL] Constraint Trigger's referenced_table

2007-12-23 Thread Richard Broersma Jr
--- On Sun, 12/23/07, Tom Lane [EMAIL PROTECTED] wrote: (and, depending on which trigger you are talking about, perhaps make it hold by changing the other table). Okay, I take it that changing the other table would only apply to tables that were designed with foreign key constraints that

[GENERAL] possible psql \d bug in 8.3 beta2

2007-12-23 Thread Richard Broersma Jr
Is seems that \d is missing the following entry when I set search_path to display two schemas: List of relations Schema |Name | Type | Owner -+-+---+-- project | managers| table | teaminst instrumentation= select version();

Re: [GENERAL] possible psql \d bug in 8.3 beta2

2007-12-23 Thread Tom Lane
Richard Broersma Jr [EMAIL PROTECTED] writes: Is seems that \d is missing the following entry when I set search_path to display two schemas: List of relations Schema |Name | Type | Owner -+-+---+-- project | managers| table |

Re: [GENERAL] possible psql \d bug in 8.3 beta2

2007-12-23 Thread Richard Broersma Jr
--- On Sun, 12/23/07, Tom Lane [EMAIL PROTECTED] wrote: -+-+---+-- project | managers| table | teaminst It's hidden by the managers table in the earlier history schema. \d without any particular schema specification will only show tables that could