RE: COUNT modifying unix timestamp

] [mailto:[EMAIL PROTECTED] Behalf Of Glenn Herbert Sent: Tuesday, February 17, 2004 9:18 AM To: U2 Users Discussion List; U2 Users Discussion List Subject: Re: COUNT modifying unix timestamp Actually, it was added in during release 7.x of uniVerse to support the SQL optimizer. The optimizer used

RE: COUNT modifying unix timestamp

to see if it needs to be resized. Vance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Glenn Herbert Sent: Tuesday, February 17, 2004 9:18 AM To: U2 Users Discussion List; U2 Users Discussion List Subject: Re: COUNT modifying unix timestamp Actually, it was added

RE: COUNT modifying unix timestamp

or do I just need to search for additional documentation? Vance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Glenn Herbert Sent: Wednesday, February 18, 2004 2:28 PM To: U2 Users Discussion List Subject: RE: COUNT modifying unix timestamp I believe

Re: COUNT modifying unix timestamp

Actually, it was added in during release 7.x of uniVerse to support the SQL optimizer. The optimizer used the count to make a determination on how long it would take to perform certain SQL operations such as outer-joins, etc, and spit out a warning message something like It will take 4307

RE: COUNT modifying unix timestamp

You don't mention the file type, but I am assuming it is a dynamic file. If it is, this is normal. I recall the first release of reliable dynamic files had the feature of disallowing access to users without 'read and write' permission...which wasn't actually documented anywhere...ouch! I think

unclassified RE: COUNT modifying Unix timestamp

David, I see the same effect on UV 10.0.15 on Win2K3 for Dynamic files, also for Dictionaries (type 3). LIST a file: no change to Windows file timestamp. COUNT the same file: Windows file timestamp is updated. ! Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL