StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Date Time Stamp column

Date Time Stamp column

Paul Chase — Thu, 02 Nov 2006 13:17:00 GMT

FYI

I tried to use the Row date time stamp column on a bo but it did not update the column after a save. I ended up implementing my own because I wanted some additional auditing functionality so I did not spend much time looking at it so it is possible it is just me not SF.

Paul

RE: Date Time Stamp column

Ivan George Borges — Thu, 02 Nov 2006 13:17:00 GMT

[quote]... using the DDT created stored procedures with the BOs and the concurrecy is going to give you the optimum performance.[/quote]

Right, I will take the optimum performance then. :)

Thanks Trent.

RE: Date Time Stamp column

Trent L. Taylor — Thu, 02 Nov 2006 11:53:30 GMT

[quote]This is done if I don't set them to be created as Stored Procedures in the DDT Table Properties, right? [/quote]

Even if you are using the DDT to create your stored procedures, and you want to use RowVersioning, you still have to set the RowVersionOrTimeStampColumn and the UpdateConcurrencyType properties on the BO for this to take effect. If you are letting the DDT create the stored procedures for you, you still have to set the InsertUsingStoredProcedure, Update..., etc. to True...but you do not have to provide the InsertStoredProcedureName, etc.

[quote]Sorry for the basic question, but what would be the advantage of both approaches ?[/quote]

Well, allowing the framework to manage your row versioning is going to be faster simply due to the fact that all of this is inline to the data saving within the framework...thus you pick up speed. Additionally, if you use the stored procedures that support the Row Versioning as well, then you gain even more speed...using the DDT created stored procedures with the BOs and the concurrecy is going to give you the optimum performance.

RE: Date Time Stamp column

Ivan George Borges — Thu, 02 Nov 2006 09:52:06 GMT

Hi Trent.

This is done if I don't set them to be created as Stored Procedures in the DDT Table Properties, right? Then I should set the properties of the BOs created in my BO Library. Sorry for the basic question, but what would be the advantage of both approaches ? That is, if I haven't got them all wrong.

Thanks.

RE: Date Time Stamp column

Trent L. Taylor — Thu, 02 Nov 2006 09:04:38 GMT

No problem...I just wanted to make sure you knew how to use it :)

RE: Date Time Stamp column

Paul Chase — Thu, 02 Nov 2006 07:57:52 GMT

Trent,

I must not have set UpdateConcurrencyType = OptimisticTimeStamp. I know that the field name was set correctly because I did double check that. Like I said I thought it might have been me.

RE: Date Time Stamp column

Trent L. Taylor — Thu, 02 Nov 2006 07:29:46 GMT

This will work because this is what we use for all of our BOs...both Row Versioning and TimeStamps. You have to set two properties:

UpdateConcurrencyType = OptimisticTimeStamp
RowVersionOrTimestampColumn = "YourDateTimeField"

That's all you have to do. The same is true for the row versioning, which is more commonly used:

UpdateConcurrencyType = OptimisticRowVersion
RowVersionOrTimestampColumn = "YourIntegerField"