On 11/21/05, Michael Fuhr <[EMAIL PROTECTED]> wrote:
> [Please copy the mailing list on replies and please don't change
> the Subject header. I've restored the original subject and am
> copying the list on this reply. I'll look at this when I get a
> chance, but maybe somebody else will answer be
[Please copy the mailing list on replies and please don't change
the Subject header. I've restored the original subject and am
copying the list on this reply. I'll look at this when I get a
chance, but maybe somebody else will answer before then.]
On Mon, Nov 21, 2005 at 05:28:30PM -, Byrne
I don't know about this particular problem, but I find in programming
in general it's always best to pass in the value of now as a
parameter, and pass it on to functions you are calling, thus avoiding
problems with mismatching values.
But as Andreas says the values should be the same within
Byrne Kevin-kbyrne writes:
> I have a trigger set up on a db - when a row is added to a certain
> table (say Table A) in my db the trigger calls a function and then the
> function enters another line in a related table (say Table B). Here's
> the problem, the first addition to Table A may show the
I have a trigger set up on a db - when a row is added to a certain table (say
Table A) in my db the trigger calls a function and then the function enters
another line in a related table (say Table B). Here's the problem, the first
addition to Table A may show the time of the addition as, for exa
