Re: Oracle, C# and ADO.net....

would it be the case that your developers are also happier with C and *nix than ms dev tools? I'd certainly be looking at moving in the direction you describe to start with.

It's also not true that the record to be updated could be updated withoutthe original user realizing. In the event that the optimistic concurrency
assumption doesn't hold then ado.net will throw a concurrency error (which can be caught and appropriately handled). See http://www.15seconds.com/issue/030604.htm for example.

You don't say how complex the apps are, and if they use stored procedures and so on, if they do then there will be work for a pl/sql developer for sure. In addition since sql server doesn't have the concept of shared sql in the same way that Oracle does, the apps won't use bind variables - using them is pretty simple, but may be new to .net developers.

On 10/25/07, Grabowy, Chris <chris.grabowy_at_lmco.com> wrote:
>
> We are cluelessly converting a few C# applications to use Oracle instead
> of SQL Server.
>
> I barely understand ADO.net, but it appears that it uses optimistic
> concurrency. Which means the record to be updated could be updated by
> another user without the original user realizing it.
>
> The current thinking is to rewrite the app back to C and host it on a
> UNIX box. While I am not a big fan of Windows, I just believe the
> rewrite to be a drastic move. So I am trying to figure what we can
> do....
>
> - I haven't used Oracle Data Provider for .NET but it "appears" to be
> what we need. Does that sound right to anyone???
>
> - We are using Oracle 10.2, so I wondering if we should do some slight
> SQL mods and use ORA_ROWSCN. Has anyone used this feature???
>
> Your clueless .net DBA,
> Chris
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

--
http://www.freelists.org/webpage/oracle-l