On Thu, Feb 26, 2009 at 1:44 AM, Quan Zongliang <quanzongliang(at)gmail(dot)com> wrote:
>> Why do we need to escape those characters? If I follow correctly, this
>> will be in an expression that the user enters themselves?
> I am sorry, Dave.
> That description is not clear. You know, my English is bad.
> There, the column mean CSV file's column, not table column.
> The end user can set a option "First row is header".
> CSV's first row will be consided column names.
> If not, they will be "Column #1, Column #2, Column #3 ..."
> Then, in the expression, the end user can input "<Column #1> || substring(<Column #3> from 2 for 1)".
> It will be convert to corresponding row's data for every statement.
Right - so why do we need to escape anything in the expression?
Shouldn't the user just be able to free-type whatever they want (in
the same way they would if they were writing the expression as part of
a query in the Query Tool?
EnterpriseDB UK: http://www.enterprisedb.com
In response to
pgadmin-hackers by date
|Next:||From: Dave Page||Date: 2009-02-26 09:06:13|
|Subject: Re: Import: empty string and expression|
|Previous:||From: Guillaume Lelarge||Date: 2009-02-26 08:29:19|
|Subject: Re: Server Status window work|