"Robert B. Easter" <[EMAIL PROTECTED]> writes: > If you use min(x) or max(x) frequently, isn't it best to make a > trigger that intercepts x on insert and update, then check it and > store it somewhere rather than scanning for it everytime? I believe that's exactly what the original questioner is trying to do... regards, tom lane
- [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 records. Chris Bitmead
- Re: [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 record... Tom Lane
- Re: [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 record... Robert B. Easter
- [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 records. Tom Lane
- [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 record... Philip Warner
- [BUGS] Re: [HACKERS] Re: [SQL] MAX() of 0 records. Philip Warner