SQL and object caching

Roelof

Hi,

In SQL it happens sometimes that object-changes are overwritten or lost, like when more developers are working in the same database. It also seems to happen when one user is re-compiling objects while someone else is still working in an object.
Is there a way to overcome these problems, or at least to reduce it to a minimum?

Thanks.

matttrax

Yep, it's called source control

No different from any other language. It can be as simple as an Excel spreadsheet with developer's initials on it or you can use tools like Subversion and Visual Source Safe. Celenia even makes a product built into Navision.

If another developer has an object checked out, you don't modify it until he/she checks it back in. Simple as that.

DenSter

There's a script that Rashed wrote in the download section that is sort of a source control. It's a table called 'Check Out' and a SQL Server table trigger on the object table. Every time an object is saved, it write a record into the check out table with the object and the user. From there on when another user tries to save the same object it raises an error, so it can only be worked on by the same user until the record is removed or the user is modified.

It's not "source control", it doesn't save individual versions of the object, but it is very helpful in keeping objects from being overwritten by other developers. I've used it in many projects and I really like its simplicity.

Roelof

Thanks, guys. I'll check it out.

Roelof

Daniel, do you have link to this?

garak

The video

The source is not here, but easy to create self.
Or you send a PM to "ara3n" and ask them if it is free.

If it is, he can also upload it to Download Section.

Regards

DenSter

I believe he has it on his blog: http://mibuso.com/blogs/ara3n/