On Fri, Sep 9, 2011 at 10:52 PM, unordained <[email protected]>wrote:
> > Anyway, my question is this: when a newer version of firebird is touching > an > older version's files (by ODS version), is it expected to go ahead and use > new > BLR codes that will be incompatible when reverting? (Yes, I know, I didn't > follow > best practices, ...) > Yes, the engine does use new BLR features on an old databases, and if you use them, you've cut off your route backward, short of doing a metadata dump (isql -x), fixing the places that don't compile on the older version, and dumping your data back to the new database created with the old software. > > And what *is* 190, anyway? > > See below. Good luck, Ann from blr.h 382#define blr_stmt_expr (unsigned char) 190 383#define blr_derived_expr (unsigned char) 191 384 385// FB 3.0 specific BLR 386 387#define blr_procedure3 (unsigned char) 192 388#define blr_exec_proc2 (unsigned char) 193 389#define blr_function2 (unsigned char) 194 390#define blr_window (unsigned char) 195 391#define blr_partition_by (unsigned char) 196 392#define blr_continue_loop (unsigned char) 197 393#define blr_procedure4 (unsigned char) 198 394#define blr_agg_function (unsigned char) 199 395#define blr_substring_similar (unsigned char) 200 [Non-text portions of this message have been removed]
