Hi! RDB$TRIGGERS.RDB$TRIGGER_TYPE was extended to BIGINT in v3, to support DDL triggers.
It was difficult to found what was going wrong with CORE-3964, but then I found it. First, INI_init checks DBB_DB_SQL_dialect_3 which works on database creation, but on opening, it's set only in PAG_header (called after INI_init). But, anyway, I don't think treating a metadata field created with a type on a dialect is going to work after that dialect is changed and the type is interpreted as another one. Also, in no way that field could be interpreted as a double, as it has bits who changes (on conversion from/to SINT64) dues to double imprecision. I have no idea what to do (well, actually I have a very easy and good one, you know, it's to wipe dialect 1/2). I'd hate to split a single field in two to support something which should be removed +10 years ago. Adriano ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
