Commented by: @dyemanov

Please provide a reproducible test case.

Commented by: Tomas Krejzek (respektive)

I'm so sorry, I forgot word "DISTINCT"

the test case is from employee.fdb distributed with firebird

CREATE VIEW UNORDERED_VIEW(
EMP_NO,
FIRST_NAME,
LAST_NAME,
PHONE_EXT,
HIRE_DATE,
DEPT_NO,
JOB_CODE,
JOB_GRADE,
JOB_COUNTRY,
SALARY,
FULL_NAME,
DEPARTMENT,
HEAD_DEPT,
MNGR_NO,
BUDGET,
LOCATION,
PHONE_NO,
COUNTRY,
CURRENCY)
AS
select distinct
EMP_NO, FIRST_NAME, LAST_NAME, PHONE_EXT, HIRE_DATE, EMPLOYEE.DEPT_NO, JOB_CODE, JOB_GRADE, JOB_COUNTRY,
SALARY, FULL_NAME, DEPARTMENT, HEAD_DEPT, MNGR_NO, BUDGET, LOCATION, PHONE_NO, COUNTRY, CURRENCY from employee
join department on employee.dept_no = department.dept_no
left join country on employee.job_country = country.country
;

The DISTINCT is crutial, on FB2.1.3 if I change first JOIN to LEFT JOIN (in my case I can, the result is same) the view work fine. On FB2.0.5 I have to remove distinct, the change JOIN to LEFT JOIN doesnt help to work fine

My post is described in firebird support list - "FB 2.1.3 - cannot order VIEW rows" from 3.2.2010

Commented by: @dyemanov

It has been already reported as CORE2863. Both tickets are closed as duplicates of CORE1089.