type ahead in 2.1b4 not working?

what you are sending is this:

SELECT DISTINCT column
FROM table
WHERE (UPPER(column) LIKE ‘H%’)
ORDER BY upper(column)

SQL Server only likes it this way

SELECT DISTINCT column
FROM table
WHERE (UPPER(column) LIKE ‘H%’)
ORDER BY column

and throws this nasty little error…

can you test youre cases again when rc2 is released later today?
I think youre case is fixed but i am not completely sure (can be a bit different)

Just to make sure: A TYPEAHEAD field should always allow every input. It should only give you options, if this is not the case in some cases please explain to me what case it exactly is and i will look into it.

All type_ahead issues should be fixed in 2.1RC3

I still have that select distinct problem with MS SQL Server in RC3…

hmm but if i remove that UPPER sort then it can be that it won’t order case insensitive anymore for some databases…

But i changed it for now so that it works on ms sql in 2.1RC4

I tested this some more. SQL Server will accept something like this:

SELECT DISTINCT UPPER(column) AS column
FROM         table
WHERE     (UPPER(column) LIKE 'H%')
ORDER BY UPPER(column)

This is actually a little strange because it seems that this is exactly what you generate.

I have also tested this from inside Servoy to see if JDBC complains - but no.

The only difference I see is the column alias?!

But this is not what i want!
The result shouldn’t be upper cased, those should be exactly what is in the db..

oops, you are right. But then SQL Server doesn’t like it…

for now i will keep it this way.
i think you can set the most databases to be caseinsensitve if you want.