Yes, the integer is needed, it's part of the spec. It's used for job
numbering. the problem being, they need not only an integer, but each
tenant needs sequential numbers.
if it was up to me, I would just remove it.
On Dec 15, 10:59 am, Eric Chamberlain wrote:
> If you are using a UUID for the p
If you are using a UUID for the primary key, do you really need an integer?
We had a similar multi-tenant need and didn't want to leak usage information to
the users, so we used UUID instead of auto incrementing integers.
On Dec 15, 2010, at 9:23 AM, Hutch wrote:
> Hi,
>
> I'm porting an old
If you are using a UUID for the primary key, do you really need an integer?
We had a similar multi-tenant need and didn't want to leak usage information to
the users, so we used UUID instead of auto incrementing integers.
On Dec 15, 2010, at 9:23 AM, Hutch wrote:
> Hi,
>
> I'm porting an old
If you are using a UUID for the primary key, do you really need an integer?
We had a similar multi-tenant need and didn't want to leak usage information to
the users, so we used UUID instead of auto incrementing integers.
On Dec 15, 2010, at 9:23 AM, Hutch wrote:
> Hi,
>
> I'm porting an old
4 matches
Mail list logo
