Not updating its timestamp livelink

toms rule #2: stop using YY, just stop -- now, forever!!! Always use to_date and ALWAYS use a 4 character year mask. You could: where dt_col between to_date( '01-jan-2002 ', 'dd-mon-yyyy hh24:mi:ss' ) and to_date( '17-jan-2002 ', 'dd-mon-yyyy hh24:mi:ss' ) or if you just wanted to supply the days as bind variables (in the form of a string like '01-jan-2002') you could: where dt_col between to_date( :bv1, 'dd-mon-yyyy' ) and to_date( :bv2, 'dd-mon-yyyy' ) (1-1/24/60/60) that would do the same (adding 1-1/24/60/60 adds 2) if you are using the mod_plsql module, you should see database sessions that are connected persistently in "stateful" mode. changing from stateless to stateful wont necessarily affect performance unless you have lots of requests coming in simultaneously and actually connecting to the database is the bottleneck (on a smallish system, this will not be the case).

Thank you, 1) toms rule #1: never compare strings to dates and dates to strings. (i still cannot believe we did not all learn this painful lesson in 2000!

Always compare strings to string and dates to dates! ) The problem you have is that: where dt_col between '01-jan-02' and '17-jan-02' is the same as: where dt_col between to_date( '01-jan-2002 ', 'dd-mon-yyyy hh24:mi:ss' ) and to_date( '17-jan-2002 ', 'dd-mon-yyyy hh24:mi:ss' ) So, the date: 17-jan-2002 (noon on jan 17th, 2002) is NOT between those two.

If you restore an old version, you will be prompted to confirm the replacement and if you select OK, the older version will be restored with a new version and the previously current version will become an old version.

If you delete the original document, all the associated versions will also be dropped with it, though you have the option to delete a particular version as shown above.

The first section, Content Approval, lets you define a protocol to make versions available to everyone with the required permission by the authorized person or else changes will remain in draft versions.

The second section, Document Version History, is the place where you enable versioning for the library.These are some of the different scenarios when Share Point will create a new version for your document or list item: Please note, although the demonstration in this tip has been shown in Share Point 2010, the versioning feature has been part of previous Share Point versions as well.Example Select the library for which you want to enable versioning in the Quick Launch on the left side (or by going to All Site Content if the library is not visible in Quick Launch), under the Library Tools ribbon, select the Library tab.Share Point allows you to enable (by default it's disabled) versioning on lists and libraries.Once enabled, Share Point will maintain multiple versions of the document or list which gets incremented on each change iteration.As I said before only major versions are created for list items and this is exactly what you see here.

Tags: , ,