Hi all,
we're experiencing some weird trouble while using the IDBroker. Two of
our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on
Postgres 8.x + Torque 3.3-RC2) start throwing duplicate key exceptions
after running (without problems) for a while. The IDs generated are much
Sorry, nothing for here similar.
2007/11/15, Hidde Boonstra [Us Media] <[EMAIL PROTECTED]>:
>
> Hi all,
>
> we're experiencing some weird trouble while using the IDBroker. Two of
> our sites (one running on MySQL 5.x + Torque 3.3-RC1 and one running on
> Postgres 8.x + Torque 3.3-RC2) start throwi
Are you having multiple servers or multiple applications access the
database? This can cause problems in the absence of transactions.
WILL
On Nov 15, 2007 5:40 AM, Hidde Boonstra [Us Media] <
[EMAIL PROTECTED]> wrote:
> Hi all,
>
> we're experiencing some weird trouble while using the IDBroker
Hi will,
thanks for your response.
No, I don't. I have thought about the possibility of transactions (or
the lack of transactions) causing the problem, but since it also occurs
with Postgres I thought I could rule it out. The weird thing is that the
id_table states (for example) a next id of
What types are you using?
are you sure you are not hitting a maximum somewhere? Short.MAXIMUM is only
32767
"Hidde Boonstra [Us Media]" <[EMAIL PROTECTED]> wrote: Hi will,
thanks for your response.
No, I don't. I have thought about the possibility of transactions (or
the lack of transactions)
11/15/07 12:02Subject
PM Re: id
Thanks Adam & Alvaro,
I use a normal size integer, so I should be save for a while. The case
of the table name is a good issue. I have been struggling with MySQL and
the id_table for a while. I have checked both databases, but alas, no
double id tables. I think I'll fall back to Torque 3.2 for
