Re: Enum type emulation: problem with opaque type in PL/pgSQL functions - Mailing list pgsql-hackers

From Max Fonin
Subject Re: Enum type emulation: problem with opaque type in PL/pgSQL functions
Date
Msg-id 20001124130214.339bf000.fonin@ziet.zhitomir.ua
Whole thread Raw
In response to Re: Enum type emulation: problem with opaque type in PL/pgSQL functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Enum type emulation: problem with opaque type in PL/pgSQL functions
List pgsql-hackers
On Thu, 23 Nov 2000 11:13:28 -0500
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Max Fonin <fonin@ziet.zhitomir.ua> writes:
> > I guess the problem is that PL/pgSQL doesn't handle opaque type correctly.
>
> No it doesn't, which is not surprising considering that opaque isn't
> really a type at all.  The error message could be improved though :-(

Well, I understood that the C is the only way very quick.
Really, OPAQUE is just reference type like char* or void*, isn't it ?

OK, I implemented emulation and now have some working version at http://ziet.zhitomir.ua/~fonin/code/my2pg.pl.
This is MySQL->Postgres dump converter and I've succeed with loading my production MySQL database converted
with it to Postgres.
However it still needs manuall correction (see BUGS section in POD).

BTW, can't somebody tell me when PG 7.1 will be released :) ?

> Currently I believe that the only way to write datatype I/O routines
> is to do it in C, because what they really need to deal in is C-style
> strings, and those are not an SQL-level type.
>
>             regards, tom lane

Thanks,
Max Rudensky.

pgsql-hackers by date:

Previous
From:
Date:
Subject: Bug with CREATE TABLE .....
Next
From: Giuseppe Tanzilli - CSF
Date:
Subject: Fields Case problem