Re: CSVQL? CSV SQL? tab-separated table I/O? RENAME COLUMN
| От | David G. Johnston |
|---|---|
| Тема | Re: CSVQL? CSV SQL? tab-separated table I/O? RENAME COLUMN |
| Дата | |
| Msg-id | CAKFQuwZFb5YFB4HUxh4swSNn4jUBV3oqFyh2RWrUiLNWUExB1g@mail.gmail.com обсуждение исходный текст |
| Ответ на | CSVQL? CSV SQL? tab-separated table I/O? RENAME COLUMN (Jim Michaels <jmichae35@gmail.com>) |
| Ответы |
Re: CSVQL? CSV SQL? tab-separated table I/O? RENAME COLUMN
|
| Список | pgsql-general |
On the whole this email is very confusing/hard-to-follow...
what do you think about foreign data wrappers getting CSV file table I/O?
I don't understand the question...
I had thought that CSVQL db could be implemented completely with
small amount of memory and file I/O, line at a time
Do you no longer think that then?
I don't see PostgreSQL being all that open to implementing a second query language beside SQL - and doing it functionally seems unlikely unless, like with JSON, you are storing entire CSV files in a table field.
- the microsoft patented CSV would be required for implementation. it
handles special data with commas and double-quotes in them
If true this seems like a show-stopper to anything PostgreSQL would implement
- biggest needed feature is an easier-to-use ALTER TABLE RENAME. a
memorable alternative/alias would be simply RENAME COLUMN columnName
TO newColumnName.
I don't see us adding new syntax for this...
David J.
В списке pgsql-general по дате отправления: