Stanley Sufficool wrote:
If the dblib methods can't behave the same as the postgres methods, > then clearly they shouldn't be named the same.
Yes, DBLIB behaves the same as pgsql in that it performs the copy in a transaction state and also has it's data visible from the server perspective. So would SQLite 2.x "COPY", IBM "EXPORT", MySQL "SELECT ... INTO OUTFILE", etc...
Firebird will work with external tables as well. But the basic point that we still do not seem to agree on is what SHOULD the target be for generic functions? It has already been decided that PDO will do nothing with SQL ... something I still disagree with ... but these copy functions are JUST different SQL procedures internally to the database.
( And should this discussion be on internals or PDO so I've retained both in the address list since I only had the pdo list in my return address process :( )
-- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
