Re: OleDb DataFactory bug. Watch out.
- From: "Nicholas Paldino [.NET/C# MVP]" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 16 Nov 2006 16:53:16 -0500
Bob,
I almost would NEVER use the OleDbFactory class to generate commands for
me. SqlFactory is one thing, since it is tailored specifically for Sql
Server. However, OleDb has to deal with a plethora of different providers
(the same thing applies for the OdbcFactory as well).
Are you writing a general-purpose tool, or are you writing something
more specific?
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
"Bob" <bob@xxxxxxxxxxx> wrote in message
news:O72lg8bCHHA.3228@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Using the OleDb factory.
Asked it to insert 4K records into a SQLAnywhere database table.
Runs out of steam at record 244 and starts writing corrupted versions of
243 primary index column until at 248 it hits a variation it has already
written and fails with a non-unique primary index error.
Use a hand rolled OleDb command and the data is written OK. Likewise the
SQL
Factory writes the same data to an SQLServer OK.
It is not a race condition as you can step through the failing iteration
and
it still fails.
So...
Stay away from the OleDb Data factory until it is repaired.
Bob
.
- Follow-Ups:
- Re: OleDb DataFactory bug. Watch out.
- From: Bob
- Re: OleDb DataFactory bug. Watch out.
- From: Bob
- Re: OleDb DataFactory bug. Watch out.
- References:
- OleDb DataFactory bug. Watch out.
- From: Bob
- OleDb DataFactory bug. Watch out.
- Prev by Date: Re: How to copy one object to another?
- Next by Date: System.Security.Cryptography.MD5.Create( ??? )
- Previous by thread: OleDb DataFactory bug. Watch out.
- Next by thread: Re: OleDb DataFactory bug. Watch out.
- Index(es):
Relevant Pages
|
