Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

Forum bugs


Go to End


3 Posts   2271 Views

Avatar
Sam

Administrator, 690 Posts

28 July 2007 at 8:37am

It's possible that it happens when two posts are added simultaneously - hence the rare occurrence of the issue.

In the NZCT branch there is a change to the ID generation in DataObject::write() - can you check to see if SS is running with this code?

The ID should *not* be generated with DB::getNextID() - instead, it inserts a blank record and passes that to the rest of the write code.

Avatar
xmedeko

Community Member, 94 Posts

29 July 2007 at 5:11pm

Edited: 29/07/2007 5:12pm

Yeah, there's
[code php]
$this->record['ID'] = DB::getNextID($ancestry[0]);
in DataObject:write()

Can you post your patch here as well, pls?
Thx

Avatar
xmedeko

Community Member, 94 Posts

31 July 2007 at 3:42pm

thanks, i've applied that.