Re: Import: empty string and expression
От | Dave Page |
---|---|
Тема | Re: Import: empty string and expression |
Дата | |
Msg-id | 937d27e10902240503k74cd8d31v674626b3929541f0@mail.gmail.com обсуждение исходный текст |
Ответ на | Import: empty string and expression (Quan Zongliang <quanzongliang@gmail.com>) |
Ответы |
Re: Import: empty string and expression
Re: Import: empty string and expression |
Список | pgadmin-hackers |
On Tue, Feb 24, 2009 at 9:23 AM, Quan Zongliang <quanzongliang@gmail.com> wrote: > Hi, all > > String: > How to distinguish NULL and empty? > > In the COPY command, it conside no quoted empty as NULL and quoted ones as empty. > This rule not defined in the CSV standard(RFC4180). > For example: > A,,B has three item: 'A', NULL and 'B' > A,"",B has three item: 'A', empty and 'B' > Should we follow this rule? > I think it is good. Sounds good to me. > Now, I use <column-name> style in the expression. > The delimiter option use this style too. (<TAB> means TAB char.) > Exscaped char is XML-style, & < and > , and so on. Why do we need to escape those characters? If I follow correctly, this will be in an expression that the user enters themselves? > Because I noticed pgAdmin has a option "Show NULL values as <NULL>". > Is it appropriate? For entering non-printable characters shouldn't we just accept whatever PostgreSQL will? Or am I missing the point? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgadmin-hackers по дате отправления: