The problem is this application is a url shortener and requires an
identifier that can be hashed and
used for those purposes. I don't know of another solution while
On Jun 8, 2:49 am, Ken Egozi <egoz...@gmail.com> wrote:
> select MAX is definitely wrong for the reasons mentioned.
> I would avoid Identity behaviour anyway, and not only because of the
> sharding issue. Using Identity means that every Insert must immediately call
> the database. This is not always desirable, as you might want to do more
> stuff with the Id, but postpone the DB call for later for various reasons.
> Now using the ObjectId approach has its limitations also, mainly the size
> The docs for Hibernate/NHibernate are all full with reasons to avoid
> > Beware of concurrency issues: two reades may read MAX() = 10 and then
> > /Jørn
> > On Jun 8, 8:19 am, SaraC <sarajchi...@gmail.com> wrote:
> > > I understand that the Mongo Ids are timestamps and can be used as
> > > Thanks a bunch!
> > --
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.