| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Konstantin Izmailov <kizmailov(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: information_schema.columns changes needed for OLEDB |
| Date: | 2009-05-24 09:32:37 |
| Message-ID: | 4A191435.8000209@xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
> On 5/23/09 7:37 PM, Konstantin Izmailov wrote:
>> Number 4 is actually numeric_precision (I typed incorrectly). My
>> recollection is that numeric_precision sometimes expressed in radix 2
>> and it caused issues for Windows apps.
>>
>> I agree on other issues. I was curious if database can help OLEDB driver
>> (to make it simpler). Anyway it can emulate values for specific Windows
>> apps on the fly. Thank you!
>
> You could, of course, create your own ms_information_schema which had
> ms_friendly views of the IS.
>
This is what I have done for a past project. I do not think we should
part from the standard SQL schema in order to satisfy a certain third
party component.
If the information_schema does not provide all the information, one
could always query the pg_* tables for needed data.
--
Regards,
Gevik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2009-05-24 11:43:51 | Re: generic options for explain |
| Previous Message | Pavel Stehule | 2009-05-24 07:34:20 | proposal: SQL parser integration to PL/pgSQL |