提交 5ce810e3 authored 作者: Thomas Mueller's avatar Thomas Mueller

Documentation.

上级 51004de0
...@@ -628,6 +628,10 @@ and the server, because the password is readable to the attacker. ...@@ -628,6 +628,10 @@ and the server, because the password is readable to the attacker.
Also, it is currently not possible to use encrypted SSL connections. Also, it is currently not possible to use encrypted SSL connections.
Therefore the ODBC driver should not be used where security is important. Therefore the ODBC driver should not be used where security is important.
</p> </p>
<p>
The first connection that opens a database using the PostgreSQL server needs to be an administrator user.
Subsequent connections don't need to be opened by an administrator.
</p>
<h3>Using Microsoft Access</h3> <h3>Using Microsoft Access</h3>
<p> <p>
......
...@@ -18,7 +18,10 @@ Change Log ...@@ -18,7 +18,10 @@ Change Log
<h1>Change Log</h1> <h1>Change Log</h1>
<h2>Next Version (unreleased)</h2> <h2>Next Version (unreleased)</h2>
<ul><li>The SQL state of the following exceptions has been changed: <ul><li>PgServer: non-admin users could not open a database.
</li><li>Non-admin users could not open a database using a mode (MODE=xxx)
if the database was already open, even if the mode matched.
</li><li>The SQL state of the following exceptions has been changed:
From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...". From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
</li><li>There is a problem when opening a database file in a timezone that has different </li><li>There is a problem when opening a database file in a timezone that has different
daylight saving rules: the time part of dates where the daylight saving doesn't match daylight saving rules: the time part of dates where the daylight saving doesn't match
......
...@@ -546,6 +546,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>. ...@@ -546,6 +546,7 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>TRANSACTION_ID() for in-memory databases. </li><li>TRANSACTION_ID() for in-memory databases.
</li><li>TRANSACTION_ID() should be long (same as HSQLDB and PostgreSQL). </li><li>TRANSACTION_ID() should be long (same as HSQLDB and PostgreSQL).
</li><li>Oracle compatibility: convert empty strings to null. </li><li>Oracle compatibility: convert empty strings to null.
</li><li>Support [INNER | OUTER] JOIN USING(column [,...]).
</li></ul> </li></ul>
<h2>Not Planned</h2> <h2>Not Planned</h2>
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论