Hi Christopher, 2009/10/19 Christopher Jones <christopher.jo...@oracle.com>: > The new interface combines system generated error messages with user > generated messages.
I think you're talking about Oracle. > The original PostgreSQL example I saw seemed to use arbitrary text > messages, similar to Oracle's DBMS_OUTPUT (page 181 of > http://tinyurl.com/UGPOM). Page 191, this document explain how DBMS_OUTPUT raise informations, which can be got with the RFC's method. > The MySQL examples in the RFC are seem to > be similar to Oracle's compilation warnings (page 167 of > http://tinyurl.com/UGPOM). Page 177 there's a "PL/SQL Success With Information Warnings" paragraph. It talks about warning raised *only* by the Oracle system. It is like MySQL, you're true. The problem is that are you really wanted this warning ? I think that yes because it helps to debug, like others warning in MySQL and PostgreSQL. > I think two message types should be handled separately. Why not... But the problem is that execution time will increase because we'll have to exec two queries ! Why not because if we do that, we have to change the PDO::ATTR_LOG_NOTICES param. I don't really agree to that. Why not developp a Oracle function which will returns a compilation of these warnings ? It must be better ! Moreover, theses warnings / notices seens to be equal... Why differents methods to get them ? Regards, Samuel. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
