User: kz Date: 05/01/21 08:38:05 Modified: /dba/connectivity/inc/connectivity/ dbexception.hxx
Log: INTEGRATION: CWS dba22 (1.10.104); FILE MERGED 2004/12/20 15:55:41 fs 1.10.104.1: convenience constructor taking a single string, for #i39187# File Changes: Directory: /dba/connectivity/inc/connectivity/ ============================================== File [changed]: dbexception.hxx Url: http://dba.openoffice.org/source/browse/dba/connectivity/inc/connectivity/dbexception.hxx?r1=1.10&r2=1.11 Delta lines: +9 -3 ------------------- --- dbexception.hxx 6 Oct 2003 15:36:49 -0000 1.10 +++ dbexception.hxx 21 Jan 2005 16:38:03 -0000 1.11 @@ -113,9 +113,15 @@ SQLExceptionInfo(const ::com::sun::star::sdbc::SQLException& _rError); SQLExceptionInfo(const ::com::sun::star::sdbc::SQLWarning& _rError); SQLExceptionInfo(const ::com::sun::star::sdb::SQLContext& _rError); - // these ctors don't make much sense anymore ... Smart-UNO had some kind of self-made rtti for exceptions, - // so we needed only the first ctor to correctly determine the exception type, but now with UNO3 - // you have to catch _all_ kinds of exceptions derived from SQLException and use the appropriate ctor ... + + /** convenience constructor + + If your error processing relies on SQLExceptions, and SQLExceptionInfos, you still may + need to display an error which consists of a simple message string only. + In those cases, you can use this constructor, which behaves as if you would have used + an SQLException containing exactly the given error message. + */ + SQLExceptionInfo( const ::rtl::OUString& _rSimpleErrorMessage ); SQLExceptionInfo(const SQLExceptionInfo& _rCopySource); --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
