You are correct it is not, but it is a valid MySQL
datatype.  The addition of the datatype is a small
part of the issue.  Torque also generates additional
indexes where it shouldn't and that can lead to poor
db performance.  

If I designate 3 fields a "primary" (A,B,C), torque
will generate the following indexes:

primary(A,B,C)
index(B,C)
index(C)

That is incorrect.  I would eventually like to change
it, but I'm starting small.

--josef
--- "Frank W. Nolden" <[EMAIL PROTECTED]> 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.
> 
>   ----- Original Message ----- 
>   From: Colm McCartan 
>   To: Turbine Users List 
>   Sent: Thursday, December 13, 2001 11:02
>   Subject: Re: adding new types to Torque..mysql
> 
> 
> 
> 
>   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)
> 
>   Good luck,
>   colm
> 
> 
> 
> 
>   --
>   To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]>
>   For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to