Hi,

The reason might be that only the dtd knows about the default values for
some attributes. The XML parser already fills in the default values if it
reads the dtd. The application itself does not do any checks, but always
uses the values from the XML parser, so the error goes unnoticed.

I will see if some checks can be built into the application to check if
required attributes are there, in order to be able to discover the error
more easily.

   Thomas

[EMAIL PROTECTED] schrieb am 03.06.2005 17:52:48:

> Figured out the problem.  This line was commented out in my schema file
> (because we had problems with it early on).  I am not sure why this would
> cause this problem.
>
>
> <!DOCTYPE database SYSTEM
>  "http://db.apache.org/torque/dtd/database_3_1.dtd";>
>
>
> Thank you to all for your help!
>
>
>
>
>
> Regards,
>
>
> C. Jason Harrelson
>
>
>
>
>
>
>

>                       Thomas Fischer

>                       <[EMAIL PROTECTED]          To:
> "Apache Torque Users List" <[email protected]>
>                       t>                             cc:

>                                                      Subject: RE :
> IDBroker problems
>

>                       06/02/05 10:23 AM

>                       Please respond to

>                       "Apache Torque Users

>                       List"

>

>

>
>
>
>
>
>
>
> Hi,
>
> this might be this bug:
>
> http://issues.apache.org/scarab/issues/id/TRQS296
>
> There was also a discussion in the users list about this some weeks ago.
>
>    Thomas
>
> "KERNEUZET FREDERIC" <[EMAIL PROTECTED]> schrieb am
02.06.2005
> 15:37:07:
>
> > Hi everybody,
> >
> > I'm also getting some trouble with (i think) my ID_TABLE :
> > Since a couple of days, we're getting some PRIMARY KEY Violation on
> > a "big" table. This is the biggest table of the application, where
> > we insert data each time an "business object" is saved (to get an
> > excellent trace of users actions).
> > ID are managed by IdBroker, so i'm wondering how could a conflict
> > exists between to object of this table ?
> > The quantity seems to be OK comparing to this table (4590).
> >
> >
> > Has someone got an idea about this ?
> > Thanks a lot.
> >
> >
> > -------- Message d'origine--------
> > De:   Dressler,Erik(externe MA) [mailto:[EMAIL PROTECTED]
> > Date:   jeu. 02/06/2005 09:24
> > �:   'Apache Torque Users List'
> > Cc:
> > Objet:   RE: IDBroker problems
> >
> > hi!
> >
> > that was no try! that was definitely an error!
> >
> > the id-table needs an init-value itself. something like this:
> >
> > insert into ID_TABLE (id_table_id, table_name, next_id, quantity)
VALUES
> > (1100, 'ID_TABLE', 1000, 10)
> >
> > greetz, erik
> >
> > > -----Original Message-----
> > > From:   Jason Harrelson [SMTP:[EMAIL PROTECTED]
> > > Sent:   02 June 2005 04:41
> > > To:   'Apache Torque Users List'
> > > Subject:   RE: IDBroker problems
> > >
> > > I tried this to no avail.  Once again the record is added to the
table
> > > with
> > > a primary key of 0.  Of course the next record still fails as it
tries
> to
> > > insert another primary key of 0.
> > >
> > > Thanks for the try.  Any other ideas out there?
> > >
> > > -----Original Message-----
> > > From: Dressler,Erik(externe MA)
[mailto:[EMAIL PROTECTED]
>
> > > Sent: Friday, May 27, 2005 5:48 AM
> > > To: 'Apache Torque Users List'
> > > Subject: RE: IDBroker problems
> > >
> > >
> > > i think i can help you!
> > >
> > > look at this row: defaultIdMethod="idBroker">
> > >
> > > xml is case sensitive. you have to write: defaultIdMethod="idbroker">
> > >
> > > good luck, drezze
> > >
> > >
> > > > -----Original Message-----
> > > > From:   Jason Harrelson [SMTP:[EMAIL PROTECTED]
> > > > Sent:   27 May 2005 04:33
> > > > To:   [email protected]
> > > > Subject:   IDBroker problems
> > > >
> > > > I am new to Torque.  I have been successful at creating my DB and
> > > classes.
> > > > Everything works correctly, excluding the primary key incrementing,
> or
> > > > populating at all.  When I add a record to my account table, I get
a
> 0
> > > > in the primary key column.  A second record added also yields a 0,
> > > > thus it fails.
> > > >
> > > > Here is an excerpt from my schema file for the account table:
> > > >
> > > > <database
> > > >
> > > > name="recipe"
> > > >
> > > > defaultIdMethod="idBroker">
> > > >
> > > > <table name="account" description="">
> > > >
> > > > <column
> > > >
> > > > name="account_id"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="true"
> > > >
> > > > type="INTEGER"
> > > >
> > > > description="Key of the account record"/>
> > > >
> > > > <column
> > > >
> > > > name="account_type"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="INTEGER"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="name_first"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="25"
> > > >
> > > > description="User's first name"/>
> > > >
> > > > <column
> > > >
> > > > name="name_last"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="25"
> > > >
> > > > description="User's last name"/>
> > > >
> > > > <column
> > > >
> > > > name="street_address"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="35"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="city"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="25"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="state"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="2"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="zip"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="9"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="email"
> > > >
> > > > required="false"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="50"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="password"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="10"
> > > >
> > > > description=""/>
> > > >
> > > > <column
> > > >
> > > > name="nickname"
> > > >
> > > > required="true"
> > > >
> > > > primaryKey="false"
> > > >
> > > > type="VARCHAR"
> > > >
> > > > size="25"
> > > >
> > > > description=""/>
> > > >
> > > > </table>
> > > >
> > > >
> > > >
> > > > The id_table has an entry for account with next_id = 1000 and
> quantity
> > > > = 10.
> > > >
> > > >
> > > >
> > > > I am not sure what else to post to help with the putting anyone on
> the
> > > > correct trail.  Everything else seems to be working correctly.  I
> have
> > > > combed the archives and found nothing similar to this problem.  If
> you
> > > > need any other info, please let me know and I will provide it.
> > > >
> > > > Thank you in advance for you help.
> > > >
> > >
> > > *  *  *  *  *  *  D I S C L A I M E R  *  *  *  *  *  *  *
> > >
> > > This message is confidential and intended for the named addressee(s)
> only.
> > > If you are not the intended recipient, please contact the sender by
> E-Mail
> > > return and then delete this message from your system. You should not
> copy
> > > or
> > > use it or disclose its contents to any other person.
> > >
> > > If any part of this message is illegible or if you suspect that the
> > > message
> > > may have been intercepted or amended, please contact the sender.
> > > Dresdner Bank Luxembourg S.A. cannot accept any responsibility for
the
> > > accuracy or completeness of this message without further
investigation.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]
> >
> > *  *  *  *  *  *  D I S C L A I M E R  *  *  *  *  *  *  *
> >
> > This message is confidential and intended for the named addressee(s)
> only.
> > If you are not the intended recipient, please contact the sender by
> E-Mail
> > return and then delete this message from your system. You should not
copy
> > or use it or disclose its contents to any other person.
> >
> > If any part of this message is illegible or if you suspect that the
> message
> > may have been intercepted or amended, please contact the sender.
> > Dresdner Bank Luxembourg S.A. cannot accept any responsibility for the
> > accuracy or completeness of this message without further investigation.
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
> ---------------------------------------------------------------------
> 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]
>


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

Reply via email to