[FX.php List] Database table modification

[Karstyn McCoy]

Duncan,

Using Record Count can be misleading.

Simple scenario - 1 record, it gets deleted and a new record created -
still 1 record.


--Karstyn



On Thu, May 13, 2010 at 7:24 AM, Duncan, Blair <Blair.Duncan at bbdo.ca> wrote:
> Thanks, you triggered something there.
> I don’t need a sort, all I need to do is a quick find.
> The result is instant!
>
> So the process is this for each table.
> Show all records.
> Check found count vs previously recorded foundcount and if not the same
> there has been a change.
> (that takes care of possible deletions that would not show up in the next
> step.)
>
> Search for modifiedtimestamp > previously recorded timestamp, if any found
> there has been a change.
>
>
>
> Blair Duncan | Variable Data Manager
> SGL Communications | 2 Bloor St W, Suite 3100 Toronto ON M4W 3R6
> T 416-413-7537 | C 416-845-3357 | F 416-972-5656
>
>
>
> -Original Message-
>
> Please make a 1 to 1 related table with the calc fields and see if it
> speeds up the process.
>
> ggt
>
> 2010/5/13 Tim 'Webko' Booth <tim at nicheit.com.au>:
>>
>> On 13/05/2010, at 2:06 AM, Duncan, Blair wrote:
>>
>> Just as a followup...
>>
>> My hacky solution although a bit faster still takes an incredibly long
>> time
>> 10 seconds or so to process, which is far too long - just to determine if
>> a
>> table has been modified.
>>
>> Here is where I am at:
>> I have a table with about 15,000 records, the table has about 80 fields
>> 3/4
>> of which are unstored calcfields.
>> Accessed through a layout that contains a single autoentered
>> modifiedtimestamp field.
>>
>> I also have another table similar to the one above above.
>>
>> In PHP, I call a preFindScript that goes to each layout, sorts on the
>> modified timestamp field and goes the last record.
>> Comparing the timestamp and record count with a pre-recorded timestamp and
>> record count enable me to determine if the table has been modified.
>> Sorting seems to take the time which I thought that since the field is
>> indexed would be much quicker.
>>
>> The larger the set, the longer the sort  time - if you are fairly sure
>> that
>> *something* should have been modified in the last (24 hours / 2 days /
>> week)
>> - perform a find and sort on the results...
>> Cheers
>> Webko
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
> -Original Message-
>
> Please consider the environment before printing this e-mail.
>
> This message and any attachments contain information, which may be
> confidential or privileged. If you are not the intended recipient, please
> refrain from any disclosure, copying, distribution or use of this
> information. Please be aware that such actions are prohibited. If you have
> received this transmission in error, kindly notify us by e-mail to
> helpdesk at bbdo.com. We appreciate your cooperation.
>
>
>
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>