Re: [Tsheetx-developers] Simple timesheet editing

[Peter L. <pal...@gm...>]

Sorry, forgot to copy the list

On 05/17/2011 09:45 AM, Peter Lazarus wrote:
> Haha, ah yes, I forgot about data aggregation. And of course that 
> reminds me of the times crossing daily boundaries. Ok, I am going to 
> abandon the simple.php cause for now and go work on something else. 
> (I've got an Android application that needs updating :-) )
>
> Regarding my son's issue, and the bug reported in Mantis, you think 
> it's limited by the post size? I must look into that, and then if that 
> works, I can close off the Mantis bug as well. Thanks Scott.
>
> Peter
>
> On 05/17/2011 09:38 AM, Scott Miller wrote:
>> Editing items in the database using the transaction numbers doesn't 
>> work due to the fact that the simple sheet may aggregate multiple 
>> items into a single number.  This is just one example of the types of 
>> issues you have to deal with, and why items are deleted and then 
>> re-added.
>>
>> Regarding your son's issues, raise the amount of data php is allowed 
>> to post to a sane number (32 meg for instance), instead of 
>> restricting it to a tiny amount.  In the /etc/php,ini file on linux.
>>
>> -Scott
>>
>> On Mon, May 16, 2011 at 6:24 PM, Peter Lazarus <pal...@gm... 
>> <mailto:pal...@gm...>> wrote:
>>
>>     On the subject of database integrity which I raised in my previous
>>     email
>>     on the simple timesheet:
>>
>>     I notice in task_maint.php this pop-up message:
>>
>>     if (confirm('Deleting a task which has been used in the past will 
>> make
>>     those timesheet ' +
>>                     'entries invalid, and may cause errors. This 
>> action is
>>     not recommended. ' +
>>                     'Are you sure you want to delete this task?'))
>>
>>     There is a recognition of creating errors by deleting a task. 
>> This is
>>     all about database integrity, but it's not handled at all well.
>>
>>     task_action.php deletes entries from the task_table and the
>>     task_assignments table, which leaves all the times table entries
>>     with a
>>     task number that no longer exists. I guess at the time it was a
>>     bit too
>>     complex a situation to handle and wasn't cleanly implemented.
>>
>>     But it is an illustration of why data integrity is important, and 
>> that
>>     we should code for it.
>>
>>     A database is a different entity to a collection of files.
>>
>>     Peter
>>
>>     
>> ------------------------------------------------------------------------------
>>     Achieve unprecedented app performance and reliability
>>     What every C/C++ and Fortran developer should know.
>>     Learn how Intel has extended the reach of its next-generation tools
>>     to help boost performance applications - inlcuding clusters.
>>     http://p.sf.net/sfu/intel-dev2devmay
>>     _______________________________________________
>>     Tsheetx-developers mailing list
>>     Tsh...@li...
>> <mailto:Tsh...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>>
>>