Sybase SQL Anywhere 12.0.1.4127 This script to reproduce the problem:
Execute SQL-query
why the error occurs:
although if you run the same query, but in the section "order by", specify the UDF without owner, there is no error:
At the same time in Sybase SA 8.0.3.5594 both SQL-query executed without error. asked 10 Sep '14, 06:56 Stalker |
Thank you for the bug report. I have opened this as CR #771044 with our development group. answered 19 Sep '14, 12:54 Jeff Albion |
It turned out there has an update that fixes this bug ? What is his number (build) ? answered 27 May '15, 10:46 Stalker CR#771044 was fixed in 16.0.0.2017 and 12.0.1.4165. 16.0 SP21 and greater should have this fix, as well as 12.0 SP81 and later (for Windows).
(27 May '15, 13:02)
Mikel Rychliski
================(Build #4165 - Engineering Case #771044)================ The server may have incorrectly returned the error: 'Function or column reference to '<user-name>' in the ORDER BY clause is invalid', if a select statement used a user-defined function with an owner name in the ORDER BY clause; e.g. ORDER BY <user-name>.<function-name(...). this="" has="" been="" fixed.="" <="" pre="">
(27 May '15, 13:22)
Breck Carter
|
Can You give a link to this fix (EBF) or a link to SQLA1201_Developer.ehe which includes this fix ? answered 28 May '15, 07:49 Stalker The good news: SQL Anywhere can show you how to download that EBF:
(28 May '15, 10:46)
Reimer Pods
Replies hidden
Though that seems often not to point out to the newest EBFs... E.g. I have 12.0.1.4216 (SP86) installed on my box and the Check tells me that there is no newer version, although 12.0.1.4231 (SP88) for that platform (Windows) has been available since early March 2015...
(28 May '15, 10:56)
Volker Barth
|
The fact that the problem is that I do not support - very much it is expensive. Maybe then You (developers ASA) can issue an updated release SQLA1201_Developer.exe which will include the latest fixes ? P.S. The current release includes SQLA1201_Developer.exe only EBF 12.0.1.4134 answered 29 May '15, 10:21 Stalker |
FWIW 16.0.0.1915 has the same symptom... it's hard to imagine an explanation that does not contain the word "bug" :)
So that this error will be corrected ?