Jump to:

23481 Posts in 18965 Topics by 2878 members

General Questions

SilverStripe Forums » General Questions » SS2.8 odd database entries

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Page: 1
Go to End
Author Topic: 249 Views
  • jennymgray
    Community Member
    7 Posts

    SS2.8 odd database entries Link to this post

    I've noticed some odd corrupt records in my database and can't work out how they got there. It looks to me as if the DataObject::write() function is failing half way through.

    Basically I get a new row where everything is NULL or default value except for the creation date.

    From my reading of write() it seems as if the first step of an INSERT is to write such an 'empty' record, and then update it with the real values to be inserted. How/why is it going wrong in the middle? Why aren't there transaction wrappers around the set of statements to ensure this doesn't happen? And what's happening to the 'real' data - I'm worried that its being lost.

    Is there anything I can do to resolve this issue, or do I just periodically clean the corruptions out?

    Is SS3 any better (I haven't had a chance to look at the implications of upgrading yet)?

    If it helps, I'm running on MSSQL.


Page: 1
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.