> > I don't think this is a good idea. If someone really relied on 'current'
> > for his application, substituting 'now' for it is not going to make things
> > better. If it's done silently it will definitely make things worse.
>
> I hadn't thought about it, but I believe Peter is right. Rejecting
> 'current' is better than silently translating it to 'now'. We have
> removed this feature and we shouldn't try to paper over the fact.
My only question is how many people were using current thinking it
functioned as 'now'? Was current ever a desired feature?
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
