Frank I'm sure you're correct that it might not be a great idea to *alter* these but in my case (and maybe Josef's) I had a blank entry for BIGINT in my postgres db.props and I was able to successfully generate a schema after adding the int8 entry (apart from the fact that torque generates incorrect sql for foreign key references to composite primary keys - another story altogether...)
colm Frank W. Nolden wrote: > MEDIUMINT is not defined in db.props file by default. You cannot just add new >keywords in this file. They have to be understood by the generation angine as well. > You can change the mapping from the already available keywords, e.g. change the >BIGINT to INT (don't why you would like to do this, but it is an example). I would >not advice you to change the mappings if you are using the latest db.props file, >since they are adapted best to the various RDBMSs. > > josef richberg wrote: > > > I'm looking to adjust the way the Mysql schema is > > created using torque. I am loooking at adding some > > keywords and modifiying the resultant .sql file. I > > looked at adding a keyword to > > tdk/share/conf/torque/templates/sql/base/mysql/db.props. > > The line I added was: > > MEDIUMINT=MEDIUMINT > > When I try to use it in type="MEDIUMINT", I get the > > following error(in velocity log): > > > > "Method get threw exception for reference $dbprops in > > /sql/base/mysql/columns.vm at [2,20]" > > > > That line is "#set ( $type = $dbprops.get($col.Type) > > )" > > > > Shouldn't this pick up the column type from the > > db.props file? > > > > --josef > > > > I tripped over the same thing - you want to change db.props in > webappname/WEB-INF/build/bin/torque/templates/sql/base rather than in > the tdk-wide share (or else, make sure you do a top-level ant build > after editing the tdk-wide copy) > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
