| From: | Steve Tucknott <steve(at)retsol(dot)co(dot)uk> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Cc: | steve(at)retsol(dot)co(dot)uk |
| Subject: | FUNCTION error and UNICODE |
| Date: | 2004-07-18 11:00:39 |
| Message-ID: | 40FA5857.6050606@retsol.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Ignore my previous messages - I have found the answers....
The FUNCTION not running was caused by my ALIAS settings - I had the
aliases defined as ALIAS AS instead of ALIAS FOR (my excuse that I
didn't spot it earlier was that I was convinced that the error message
was talking about the AS of the function definition itself - couldn't
see the wood for the trees). After a few more fixes the function is now
running fine.
The problem with UNICODE and PgAccess. I ended up uninstalling the RPM
packages and then installing and building PostGre from source. The
--with-tcl option of the configure process was the option required to
get PgAccess to work.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Loftis, Charles E | 2004-07-18 19:20:05 | SQL - Indexing for performance on uniquness check... |
| Previous Message | Markus Bertheau | 2004-07-18 10:49:39 | Re: MultyByte Question |