Dario V. Fassi wrote:
> Yes you are right , the original data come from a DB2 with CodePage
> IBM-850 and was inserted without complains in a Postgres 7.3.6 with
> SQL_ASCII.
If you have a program named "recode" installed you could try using that
to recode the dump file to a supported encoding.
Hi all,
I need ur help regarding the optimization of following
query. If possible pls reply asap.
Thankz a ton in advance.
SELECT company_name,coupon_id,coupon_title, city_name,
category_name, NVL(person_name,' ') person_name,
NVL (locality_name,' ') locality_name,
NVL(company_address,' ') com
I wrote the following:
CREATE OR REPLACE FUNCTION escritorio.seq_valor_actual( text)
RETURNS integer AS '
DECLARE
secuencia ALIAS FOR $1;
valor_actual integer := 0;
v_query text;
actual integer;
BEGIN
RAISE NOTICE ''el parametro tiene el siguiente valor %''
Tom Lane wrote:
"Dario V. Fassi" <[EMAIL PROTECTED]> writes:
A simple question, we need to migrate many (>20) postgres databases from
SQL_ASCII encoding to UNICODE encoding, over a 7.3.6 server.
SQL_ASCII is not an encoding (it's more like the absence of knowledge
about
Tom Lane wrote:
"Dario V. Fassi" <[EMAIL PROTECTED]> writes:
SQL_ASCII is not an encoding (it's more like the absence of knowledge
about an encoding). What is the data actually stored as?
Yes you are right , the original data come from a DB2 with Code
