Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Adding some dates
06-09-2012, 05:09 PM,
#8
RE: Adding some dates
(06-07-2012, 06:26 PM)phil Wrote: Hi Ricard,

As mentioned on the forum, I would prefer not to add fields for date changed field - instead upgrade the functionality in the Audit trail please.

Thanks

Hi Phil:

I have been thinking about it in detail and (to my knowledge), the best option is to add a field instead of the Audit approach:

1) Currently we already have one of these fields (lastcostupdate) and seems to be working fine and it is useful. No one complained about its existence so far. Particularly we use it extensively.

2) The Audit approach to retrieve information (other than for audit purposes) has a severe time limitation. After X months the information is deleted, so after X months we couldn't retrieve the information. Solution could be a no time limit for audit but the table would grow immensely (we add around 200.000 records to the audit per month).

3) We are not approaching any mySQL limit regarding number of fields per table, etc on stockmaster table, so should not be a problem adding one (or few more) date fields.

4) Seems logical that performance will not suffer for the cost of adding some fields. On the contrary, having an very large audit table with some milions of records will cause some performance problems retrieving data.

5) The audit function works fine for audit purposes (who did what when), but I do not think it is OK for business data extraction.

6) If the idea is to keep all changes on the audit table, what will we do with the prices table? We also keep old prices with their dates. Theoretically could be retrieved from the audit as well. Will we move into this direction? Also the same could happen to purchdata.

7) I agree that adding some fields will increase a bit the size of the database, but will keep the code easy to read and less lines to maintain. Disc bytes are cheap nowadays but brains to code aren't. So it seems wise to keep the simple code we have better than save some cents on disk usage.

8) I could not find a single technical or business reason against the option of adding a useful field to one table.

Well, I'm open to change my mind if I'm wrong. Any other developers agree? Disagree? What could be improved?


Regards,
Pak Ricard
Reply


Messages In This Thread
Adding some dates - by PakRicard - 06-06-2012, 05:42 PM
RE: Adding some dates - by opto - 06-07-2012, 07:56 AM
RE: Adding some dates - by PakRicard - 06-07-2012, 11:47 AM
RE: Adding some dates - by phil - 06-07-2012, 12:00 PM
RE: Adding some dates - by PakRicard - 06-07-2012, 05:22 PM
RE: Adding some dates - by phil - 06-07-2012, 06:26 PM
RE: Adding some dates - by PakRicard - 06-09-2012, 05:09 PM
RE: Adding some dates - by PakRicard - 06-08-2012, 10:40 AM
RE: Adding some dates - by phil - 06-09-2012, 06:21 PM
RE: Adding some dates - by PakRicard - 06-09-2012, 07:54 PM
RE: Adding some dates - by phil - 06-10-2012, 01:31 PM
RE: Adding some dates - by PakRicard - 06-10-2012, 02:22 PM
RE: Adding some dates - by Exsonqu_Qu - 06-10-2012, 08:42 PM
RE: Adding some dates - by phil - 06-11-2012, 07:35 AM
RE: Adding some dates - by PakRicard - 06-11-2012, 11:41 AM
RE: Adding some dates - by phil - 06-12-2012, 08:46 AM
RE: Adding some dates - by PakRicard - 06-12-2012, 12:05 PM
RE: Adding some dates - by Exsonqu_Qu - 06-13-2012, 01:27 PM
RE: Adding some dates - by PakRicard - 06-14-2012, 06:29 PM
RE: Adding some dates - by phil - 06-14-2012, 07:02 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)