SQL differences between SqlServer and Oracle

[janvv]

I have an application which should be working with SqlServer and Oracle.
Why do I need Unidirect? Isn't it the same as using the interfaces IDBConnection and IDBCommand?
Or does it solve Sql differences?
A query like 'select * from sometable where somedatecol < getdate()' will only work with SqlServer, and 'getdate()' should be replaced by 'sysdate' to make it work with Oracle. And this is only a simple issue. How about other sqlcommands like 'update tblA set a.col1 = b.col3, a.col2 = b.col from tblA as a, tblB as b where etc...'. This will never work on an Oracle database. Even using a UniCommand I cannot have a common sourcecode for both databases. Or don't I understand the Unidirect product?

[Oleg]

UniDirect .NET doesn't solve problems with different ways of writing SQL now.
But UniDirect .NET offers the following features:

• Universal access to data of different databases
• 100% managed code
• High performance
• Easy to deploy
• UniScript component to execute scripts
• Ability of monitoring query and stored procedures execution
• Advanced design-time editors
• Migration wizard from SQL Server, OLE DB, ODBC and Oracle .NET Data Providers
• Help integrated into Visual Studio .NET
• Free support for registered users
• Licensed per a developer without royalty fee

[chrissilein]

Hello,

do you plan to release such a component?
Are there any components which solve these
language issues??

Chris

[Oleg]

We are planning to enhance UniDirect .NET functionality in future and will add the feature with an ability of different writing of SQL but not at the nearest time.

[Guest]

Hi janvv,

as I have the same problem as you. What do you plan to do?
Pls, send me an email ([email protected]).

Best regards,

Chris