Hello Francisco,
Does the Npqsql initialize each property? i.e. if some column is not a
key, will the corresponding code succeed?
bool b = (bool)schemaTable[IsKey];
No, currently I don't use any additional metadata, thanks :).
Regards,
Konstantin Triger
Francisco Figueiredo Jr. wrote:
Hello,
I've retested my apps with the new svn version... I can now log into my
app
without this System.IndexOutOfRangeException: Array index is out of range.
But there's problem with some sql commands... with postgresql, oracle and
mssql
I think that it's when I combine several select
Hello
I've found the last problems I had...
The problem is when you do a fill with a null datetime in the result
dataset...
the problem is in method
internal void ReadIDataRecord(int recordIndex, IDataRecord record, int[]
mapping, int length)
of the record cache class
this method do a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin Triger wrote:
Hello Hubert,
There was a change during this week end: the Mainsoft changes were
merged into the trunk (they were previously available at
Mainsoft.System.Data branch).
From the stack I suppose that PG provider does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hubert FONGARNAND wrote:
I've applied your patch...
It corrects the problem with my postgresql app...
Hi Hubert!
What Npgsql version are you using??
I know that Konstantin patch adds much more reliability to the
DbDataAdapter code, but I'd like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin Triger wrote:
Hello Hubert,
Hi all!
I'm completely agree that bugs are a bad thing, that's why I'm here to
help you as soon as possible. The reason the DataAdapter code has
changed is to solve other bugs, and the solution required
I guess the following is more proper fix. But, I am not sure why there
is no GetDateTimeSafe in ISafeRecord and is there any reason to leave
this to throw exception. Kosta could clear this. Hubert, can you please
try this?
[SNIP]
Index: System.Data.Common/DataContainer.cs
You're patch has nothing changes... I get always the same error...
With the postgresql app... I can now login... but there's plenty of bugs
inside... I think the best solution is to get an older version of Mono!
Why do you include a patch if there's compatibility problems with data
providers!!!
Hello Hubert,
I'm completely agree that bugs are a bad thing, that's why I'm here to
help you as soon as possible. The reason the DataAdapter code has
changed is to solve other bugs, and the solution required some
cooperation from providers too. Unfortunately it's not simple to make
a complete
I've updated my mono this morning from SVN...
and all db applications (PostGreSQL) fails with :
System.InvalidCastException: Cannot cast from source type to destination type.
in 0x00548 System.Data.Common.DbDataAdapter:BuildSchema (IDataReader reader,
System.Data.DataTable table, SchemaType
+ bool allowDBNull =
value is bool ? (bool)value : false;
default allowDBNull should be true ;-)
suresh.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Agreed, but in fact the provider should set the defaults, not the
DataAdapter :-).
Regards,
Konstantin Triger
Sureshkumar T wrote:
+ bool allowDBNull = value is bool ? (bool)value : false;
default allowDBNull should be true ;-)
suresh.
Hello again,
Seems that Oracle provider does not initialize at all some columns in
SchemaTable.
The attached patch fixes that in a generic way.
Regards,
Konstantin Triger
Hubert FONGARNAND wrote:
I've applied your patch...
It corrects the problem with my postgresql app...
but i get always an
13 matches
Mail list logo
