| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
2) Fix a bug *passowrd prompt in case of md5 authentication*.
3) Improve the DSN setup dialog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Changes to avoid collisions with WIN32 & MFC names...
> 1. Renamed:
> a. PROC => PGPROC
> b. GetUserName() => GetUserNameFromId()
> c. GetCurrentTime() => GetCurrentDateTime()
> d. IGNORE => IGNORE_DTF in include/utils/datetime.h & utils/adt/datetim
>
> 2. Added _P to some lex/yacc tokens:
> CONST, CHAR, DELETE, FLOAT, GROUP, IN, OUT
Jan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allows you to set the loglevel at runtime by adding ?loglevel=X to the connection URL, where 1 = INFO and 2 = DEBUG.
Automatically turns on logging by calling DriverManager.setPrintWriter(new PrintWriter(System.out)) if one is not already set.
Adds a Driver.info() message that prints out the version number
Adds member variables logDebug and logInfo that can be checked before making logging methods calls
Adds a build number to the version number string. This build number will need to be manually incremented when we see fit.
----------------------------------------------------------------------
Modified Files:
org/postgresql/Connection.java org/postgresql/Driver.java.in
org/postgresql/fastpath/Fastpath.java
org/postgresql/jdbc1/DatabaseMetaData.java
org/postgresql/jdbc2/Connection.java
org/postgresql/jdbc2/DatabaseMetaData.java
org/postgresql/largeobject/LargeObjectManager.java
org/postgresql/util/PSQLException.java
org/postgresql/util/Serialize.java
----------------------------------------------------------------------
|
| |
|
|
|
|
| |
Integer for a smallint datatype instead of a Short
|
|
|
|
| |
Permaine Cheung
|
| |
|
| |
|
| |
|
|
|
|
| |
of keys
|
|
|
|
| |
handled Timestamps incorrectly
|
|
|
|
|
|
|
|
| |
with the Cursor object's fetchmany() method. The API and
inline documentation state that the default is 1. It
currently defaults to 5.
Patrick Macdonald
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Makefile.shlib system, not MakeMaker.
|
|
|
|
|
|
|
|
|
|
| |
2) Supprt ARD precision/scale and SQL_C_NUEMRIC.
3) Minimal implementation of SQLGetDiagField().
4) SQLRowCount() reports the result of SQLSetPos and SQLBulkOperation.
5) int8 -> SQL_NUMERIC for Microsoft Jet.
6) Support isolation level change.
7) ODBC3.0 SQLSTATE code.
8) Append mode log files.
|
|
|
|
|
| |
- Removed some simple rules to work arounf bison limit for now.
- Update c_keywords.c to reflect changes in keywords.c.
|
|
|
|
|
|
| |
- Synced preproc.y with gram.y.
- Synced pgc.l with scan.l.
- Synced keywords.c.
|
|
|
|
|
|
|
|
|
| |
GUC support. It's now possible to set datestyle, timezone, and
client_encoding from postgresql.conf and per-database or per-user
settings. Also, implement rollback of SET commands that occur in a
transaction that later fails. Create a SET LOCAL var = value syntax
that sets the variable only for the duration of the current transaction.
All per previous discussions in pghackers.
|
|
|
|
| |
The code was not expecting to receive notice messages during the connection handshake.
|
| |
|
| |
|
| |
|
|
|
|
| |
- Fixed a typo in a comment printed by ecpg.
|
|
|
|
|
|
|
|
|
|
|
| |
by Marcelo Aceto <aceto@newinf.com.br> .
1) Wrong translations of embedded escape sequences inside outer join escape
sequences.
2) Wrong translation of parameter markers inside outer joins and function
escape sequences.
3) Bad concatenation of date, time, timestamp constants with next word in
statement:
|
| |
|
|
|
|
| |
Zhenbang Wei
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
work on all win9x machines, so i made it go thru a l ookup table
instead, using the DLL as last resort. I also moved this out of the
fe-misc.c file because of the size of the lookup ta ble. Who knows, we
might add more other win32 specific code there in the future.
I also fixed a small typo in the pg_config.h.win32 that made the
compiler compla in about the gnu snprintf declaration.
I tried to make this patch with psql coding style. I've successfully
tested this on win2k and win98 and it works fine (i.e. the mes sage
shows on win98 too, it didn't with the old implementation).
Magnus Naeslund
|
|
|
|
|
|
|
|
|
|
|
| |
Slackware 8), and perhaps on other Pythons, haven't checked. Something in
the _pg.connect() call isn't working. I think the problem stems from the
fact that 'host' is a named parameter of both _pg.connect and pgdb.connect,
and so Python treats it as a variable assignment, not a named parameter.
Uses non-named parameters.
Andrew Johnson
|
|
|
|
|
|
| |
the new verion compiled on SCO Openserver 5.0.5 and Unixware 7.1.1
Nicolas Bazin
|
|
|
|
|
| |
2) Handle timestamp without time zone.
3) Improve SQLForeignKeys() in multibyte mode.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
added a setup/teardown to create and drop the connection, and table
|
|
|
|
| |
repaired the bug, haven't made it caseInsensitive
|
| |
|
|
|
|
|
| |
Tom Lane to move string storage to end of structure but keep pointer in
the same location.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In summary, if a software writer implements timer events or other events
which generate a signal with a timing fast enough to occur while libpq
is inside connect(), then connect returns -EINTR. The code following
the connect call does not handle this and generates an error message.
The sum result is that the pg_connect() fails. If the timer or other
event is right on the window of the connect() completion time, the
pg_connect() may appear to work sporadically. If the event is too slow,
pg_connect() will appear to always work and if the event is too fast,
pg_connect() will always fail.
David Ford
|
|
|
|
|
| |
2) Introcuced 3 drivers.
3) The version is now 7.02.0001.
|
|
|
|
| |
- Fixed one bug in structure handling resulting in using sizeof indicator instead of variable.
|
|
|
|
| |
2) Suppress some error logs for the request to other drivers.
|
|
|
|
|
|
|
|
|
|
| |
entries, per pghackers discussion. This fixes aggregates to live in
namespaces, and also simplifies/speeds up lookup in parse_func.c.
Also, add a 'proimplicit' flag to pg_proc that controls whether a type
coercion function may be invoked implicitly, or only explicitly. The
current settings of these flags are more permissive than I would like,
but we will need to debate and refine the behavior; for now, I avoided
breaking regression tests as much as I could.
|
| |
|
| |
|