Have now fixed the problem, thanks to inpuit from JMcnally. The XXX-schema-idtable-init.sql file is not generated from the row.vm template as I thought, but from a specific idtable.database file which had the column names of the id table hard coded in lower case.
CHEERS> SAM Sam Joseph wrote: > So working my way through the code I have established by adding > certain comment statements that all column names are read in and > initial stored in their upper case format. > > However when the insert statements for the id table are generated to > be placed in XXX-schema-idtable-init.sql the column names come out in > lower case. > > So far I cannot find the place where this transformation takes place > except to know that the row.vm template is used and the process would > appear to be controlled from this part of the Control.vm template > > ## Generate inserts into ID-TABLE for initial ids. > #set ( $initialID = 1 ) $generator.parse($idname, $outFile, > "tables", $database.tables) > > Thus I assume that the actual merging of the template takes place > somewhere within the bowels of Texen somewhere. > > If someone can direct me to the place where the template merging takes > place I will endeavour to fix the case sensitivity problem. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
