Re: IdBroker, Native and MSSQL

[Trey Long]

Yes, everything seems correct from my end. Here is a bit of my schema:
    <table name="underwritingApp">
        <column name="underwriterId" primaryKey="true" required="true" 
type="INTEGER" autoIncrement="true"/>
        <column name="companyId" type="INTEGER"/>
        <foreign-key foreignTable="company">
            <reference foreign="companyId" local="companyId"/>
        </foreign-key>
    </table>
It seems that if defaultIdMethod="native" then torque shouldn't attempt 
to insert fields like underwriterId. The only reason that I have not to 
use the id-broker is because torque may not be the only thing making 
inserts into the database.

What I will probably end up doing is changing the id-broker increments 
to mismatch the DB's autoenerated keys, *IF* I can get torque to insert 
into that column, which is unlikely.

-Jim

Andras Balogh wrote:
Hello,

I have successfully used Torque and MSSQL with no problems.
Are you sure you are defining in your schema  for the identity column
you have primaryKey="true" autoIncrement="true"?

Best regards,
Andras.

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


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