From: | fxjr(at)pgfoundry(dot)org (User Fxjr) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | npgsql - Npgsql2: [#1003400] Later type binding for DbType.Object |
Date: | 2008-06-22 16:21:39 |
Message-ID: | 20080622162139.DCBFA17AE707@pgfoundry.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
[#1003400] Later type binding for DbType.Object
Fixed problems with explicit parameter datatype casting. Now, whenever as parameter has a dbtype.object data type, the cast will be turned off. This will revert the flexibility of letting the type specification to postgresql itself.
If a user wants to turn cast on, just specify a dbtype value other than object or specify an NpgsqlDbType. See: http://pgfoundry.org/forum/message.php?msg_id=1003583, http://pgfoundry.org/forum/message.php?msg_id=1003620 and http://pgfoundry.org/tracker/index.php?func=detail&aid=1003400&group_id=1000140&atid=592 for discussions about that. Also, DbType.Object is mapped in NpgsqlTypesHelper as an alias to text datatype on internal mapping.
Thanks Waldemar Bergstreiser and Andrus Moor for discussions about that.
Modified Files:
--------------
Npgsql2/src/Npgsql:
NpgsqlCommand.cs (r1.22 -> r1.23)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlCommand.cs.diff?r1=1.22&r2=1.23)
NpgsqlParameter.cs (r1.14 -> r1.15)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlParameter.cs.diff?r1=1.14&r2=1.15)
Npgsql2/src/NpgsqlTypes:
NpgsqlTypesHelper.cs (r1.15 -> r1.16)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/NpgsqlTypes/NpgsqlTypesHelper.cs.diff?r1=1.15&r2=1.16)
From | Date | Subject | |
---|---|---|---|
Next Message | User Fxjr | 2008-06-22 16:48:10 | npgsql - Npgsql2: Added tests for parameter casts. |
Previous Message | Tom Lane | 2008-06-20 00:24:54 | pgsql: Seems I was too optimistic in supposing that sinval's maxMsgNum |