On 28-01-2012 00:50, Claudio Valderrama C. wrote: >> -----Original Message----- >> From: Mark Rotteveel (JIRA) [mailto:trac...@firebirdsql.org] >> Sent: Viernes, 27 de Enero de 2012 13:45 >> >> RDB$UNIQUE_FLAG is 1 for a unique index, but NULL for >> non-unique (I would expect 0) >> RDB$INDEX_INACTIVE is NULL for newly created indices (I would >> expect 0), issuing an ALTER INDEX <name> INACTIVE makes it 1 >> and 0 if it has been again altered to ACTIVE >> RDB$INDEX_TYPE is 1 for DESCENDING indices, but NULL for >> ASCENDING (I would expect 0) > > Adriano, can you confirm that you have default values for those fields in > DdlNodes.epp in v3? For what I see, we won't get nulls in v3 in those > fields, so it should be possible to make them non-nullable. >
The refactor aimed to only restructure the code but not the functionality. So I don't think it was changed, but is probably much easier to review and change it place than in the old DYN code. Adriano ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel