RE: [PROPOSAL]a new data type 'bytea' for ECPG
| От | Matsumura, Ryo |
|---|---|
| Тема | RE: [PROPOSAL]a new data type 'bytea' for ECPG |
| Дата | |
| Msg-id | 03040DFF97E6E54E88D3BFEE5F5480F737A383FB@G01JPEXMBYT04 обсуждение исходный текст |
| Ответ на | RE: [PROPOSAL]a new data type 'bytea' for ECPG ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
| Ответы |
RE: [PROPOSAL]a new data type 'bytea' for ECPG
|
| Список | pgsql-hackers |
> From: Tsunakawa, Takayuki [mailto:tsunakawa.takay@jp.fujitsu.com] > > I think the host variable data type that corresponds to the server-side bytea > should be bytea. As the following pages state or imply, it would be better > to create standard-compliant LOB types someday, and use the keyword BLOB in > ECPG for that type. The server-side data types should have the names BLOB, > CLOB and NCLOB. Those types should handle data larget than 1 GB and have the > locator feature defined in the SQL standard. Maybe we should also advanced > LOB features like Oracle's SecureFiles LOB and SQL Server's FileTables. Tsunakawa-san, thanks for your advice. I understand that C type definition of client-side bytea is not constrained by the standard BLOB. What should I do next? For now, I attach a patch that is removed noise(pgindent/typedef.list). P.S. The patch does not support ECPG.bytea in sqltype of "struct sqlvar_struct" because of compatibility. Regards Ryo Matsumura
Вложения
В списке pgsql-hackers по дате отправления: