diff options
Diffstat (limited to 'dbaccess/source/core/dataaccess/datasource.cxx')
| -rw-r--r-- | dbaccess/source/core/dataaccess/datasource.cxx | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/dbaccess/source/core/dataaccess/datasource.cxx b/dbaccess/source/core/dataaccess/datasource.cxx index 348408609f1b..f0bb910db27a 100644 --- a/dbaccess/source/core/dataaccess/datasource.cxx +++ b/dbaccess/source/core/dataaccess/datasource.cxx @@ -330,7 +330,7 @@ class OSharedConnectionManager : public OConnectionHelper_BASE typedef ::std::map< Reference< XConnection >,TConnectionMap::iterator> TSharedConnectionMap;// holds the shared connections ::osl::Mutex m_aMutex; - TConnectionMap m_aConnections; // remeber the master connection in conjunction with the digest + TConnectionMap m_aConnections; // remember the master connection in conjunction with the digest TSharedConnectionMap m_aSharedConnection; // the shared connections with conjunction with an iterator into the connections map Reference< XProxyFactory > m_xProxyFactory; @@ -1232,7 +1232,7 @@ Reference< XConnection > SAL_CALL ODatabaseSource::connectWithCompletion( const if (bNewPasswordGiven) { m_pImpl->m_sFailedPassword = m_pImpl->m_aPassword; - // assume that we had an authentication problem. Without this we may, after an unsucessful connect, while + // assume that we had an authentication problem. Without this we may, after an unsuccessful connect, while // the user gave us a password an the order to remember it, never allow an password input again (at least // not without restarting the session) m_pImpl->m_aPassword = ::rtl::OUString(); @@ -1393,8 +1393,8 @@ void SAL_CALL ODatabaseSource::flushed( const EventObject& /*rEvent*/ ) throw (R // // Since this is a conceptual problem as long as we do use those ZIP packages (in fact, we *cannot* // provide the desired functionality as long as we do not have a package format which allows O(1) writes), - // we cannot completely fix this. However, we can relax the problem by commiting more often - often - // enough so that data loss is more seldom, and seldom enough so that there's no noticable performance + // we cannot completely fix this. However, we can relax the problem by committing more often - often + // enough so that data loss is more seldom, and seldom enough so that there's no noticeable performance // decrease. // // For this, we introduced a few places which XFlushable::flush their connections, and register as |