argument. In Firebird 2, they treat NULL as the value 0: • FIRST • SKIP This new Firebird 2 directive returns an empty set if any argument is NULL: • ROWS In new code, use ROWS, not FIRST and SKIP descending sorts. You can override this default placement by adding a NULLS FIRST or NULLS LAST directive to the ORDER BY clause. In earlier versions, NULLs were always placed at the end of a sorted set is executed with Firebird 2’s gbak! • Firebird 2.0 has a bug that causes the NULLS FIRST|LAST directive to fail under certain circumstances with SELECT DISTINCT. See the bugs list for more details.

contain simpler constructs — clauses and options. Clauses A clause defines a certain type of directive in a statement. For instance, the WHERE clause in a SELECT statement and in some other data manipulation a table or column, an index with the same name is created automatically, without an explicit directive from the designer. For example, the PK_COUNTRY index will be created automatically when you execute doesn’t have a match in the other but must still be included because of the LEFT, RIGHT or FULL directive, the merged column in the joined set gets the non-NULL value. That is fair enough, but now you

contain simpler constructs — clauses and options. Clauses A clause defines a certain type of directive in a statement. For instance, the WHERE clause in a SELECT statement and in some other data manipulation a table or column, an index with the same name is created automatically, without an explicit directive from the designer. For example, the PK_COUNTRY index will be created automatically when you execute doesn’t have a match in the other but must still be included because of the LEFT, RIGHT or FULL directive, the merged column in the joined set gets the non-NULL value. That is fair enough, but now you

Win2K system with SP4 and all subsequent updates, it has been reported that an "operating system directive" exception occurred and investigation of the system log indicated that "registering" the DLLs was problem. It is suggested that you explore this route only if you encounter the operating system directive exception problem on Windows 2000 and see that advice when you follow it up in the system log.

-902 335544346 metadata_corrupt Corrupt system table -902 335544373 sys_request Operating system directive failed -902 335544384 badblk Internal error -902 335544385 invpoolcl Internal error

-902 335544346 metadata_corrupt Corrupt system table -902 335544373 sys_request Operating system directive %s failed -902 335544384 badblk Internal error -902 335544385 invpoolcl Internal error -902 335544387

-902 335544346 metadata_corrupt Corrupt system table -902 335544373 sys_request Operating system directive @1 failed -902 335544384 badblk Internal error -902 335544385 invpoolcl Internal error -902 335544387

with administrator rights) can appoint co-administrators. This is done with the GRANT ADMIN ROLE directive: Chapter 5. Server configuration and management 20 create user bigbill password 'bigsekrit7foryou'

перевод сообщения. Повреждение системной таблицы -902 335544373 sys_request Operating system directive @1 failed Директива операционной системы @1 не удалась -902 335544384 badblk Internal error

-902 335544346 metadata_corrupt corrupt system table -902 335544373 sys_request operating system directive @1 failed -902 335544384 badblk internal error -902 335544385 invpoolcl internal error -902 335544387