Re: [Phphelpdesk-help] Opinion Solicitation: Deleting/Modifying Events

[Roy R. <rs...@ae...>]

On Mon, 15 Jul 2002, Tony Gettig wrote:
>From my perspective, I would think if a person has the ability to enter
>and update tickets, that should be security enough to be able to change
>the date. Which, if I understand your application of it, is how you are
>using it at your place. If integrity of the record is ever in question,
>could the dbadmin check the timestamp of the entry? Looking at the events
>table layout, might this require an extra field in the mysql db? For
>instance, a timestamp field (already there) and an e_workdate field for
>the date entered. Just thinking out loud now.

Right now, as you noticed, there's only one field -- e_timestamp.  Changing
the schema as you suggested would work, but I'm disinclined to do this
because database changes are kind of a big deal when it comes to people
already using the product and, frankly, I don't really think it's my place
to contribute code that requires DB changes.

> I've made very few changes to the program, but this is one that I've been
> seriously considering doing. If you have plans to put this ability in the
> release, I'll likely wait. I'm not much of a programmer, preferring to
> leave such things to people that are actually good at it. :)

Well, I have plans to put this ability in the repository.  I don't actually
make any decisions about when the next version of PHPHD is released and
what is included in it -- keep in mind I'm just a PHPHD user who hounded
the project manager until he gave me access to the repository.

As for leaving coding to people that are actually good at it ... why, yes,
I should probably do that also :)

-roy