I have two tables that I am using in my test application with the Sql
defined as below:

Table 1
============

SELECT * FROM Users
WHERE UPPER(LoginName) = UPPER({LoginName='1234'})

when I try and load this table I get the following url generated:

 http://localhost:12009/Cypher1Users?method=rows&LoginName='1234'

which is correct and what I would expect.

Table 2
========
SELECT * FROM SecurityUser
WHERE UPPER(UserName) = UPPER({UserName='1234'})

when I try and load this table I get the following url generated:

http://localhost:12009/Cypher1SecurityUser?method=rows&UPPER(UserName)='1234'

Why has this put UPPER(UserName) instead of just UserName?

--
Chris Holland
[Team Elevate]

Forget it, I have found it.

I copied the SQl from the table definitions into my code and left the
UPPER() call in the code.

Chris Holland
[Team Elevate]

On 30/01/2013 06:42, Chris Holland wrote:
> I have two tables that I am using in my test application with the Sql
> defined as below:
>
> Table 1
> ============
>
> SELECT * FROM Users
> WHERE UPPER(LoginName) = UPPER({LoginName='1234'})
>
> when I try and load this table I get the following url generated:
>
>   http://localhost:12009/Cypher1Users?method=rows&LoginName='1234'
>
> which is correct and what I would expect.
>
> Table 2
> ========
> SELECT * FROM SecurityUser
> WHERE UPPER(UserName) = UPPER({UserName='1234'})
>
> when I try and load this table I get the following url generated:
>
> http://localhost:12009/Cypher1SecurityUser?method=rows&UPPER(UserName)='1234'
>
>
> Why has this put UPPER(UserName) instead of just UserName?
>