>Gerard,
>
>No this isn't a bug, it's just the way buffering works. You can run a scan loop over the view instead of going through the effort of a COPY TO.


David,

Is'nt running a Scan Loop really the same as doing a Copy. It's another process that needs to be run.

If you have a data source (i.e. The buffered data) and two commands which normally do the same thing (i.e. Copy to and Sql Select) , why should they behave any differently 'JUST' because the data is buffered ?

This beahviour really renders SQL SELECTS (with Buffered Data) useless without cumbersome workarounds . This in effect then means that one would think twice about using BUffering at all if the de facto standard these days (ie. SQL SElect) cant even be used on buffered data .

I'd be very interested to get a general view on this behaviour... the fact that 'Workarounds' have to be employed indicates a good reson for defining this as a 'Bug' rather than a 'Design Feature'

regards,

Gerard