![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Thu, Oct 1 2009 8:59 AM | Permanent Link |
QuickAndDirty | Hello everybody,
I'm still working to enable big software to work with Elevate instead of BDE. There is the following Problem: If I execute the SQL SELECT * FROM Stations WHERE NUMMER = '380' , it fails, because it does not automaticaly interpret the '380' as an Integer. Where is the switch to activate a more intelligent behavior? It is very important for me to do so because we have thousends of customized macro files that contain sqls in this way, they do work with oracle, Paradox and Microsoft sql server. Our Customers can easily switch between these databases and I hope we soon can offer elevateDB in the same way. It wood realy be a step back if using elevatedb forces us to redesign and test all the custom sqls. hoping for help QuickAndDirty |
Thu, Oct 1 2009 2:21 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | << Where is the switch to activate a more intelligent behavior? >> There isn't any switch in ElevateDB. Per the SQL standard, the SQL in EDB is strongly-typed and you cannot mix strings with integers, or vice-versa. You can find out more on type compatibility and promotion here: http://www.elevatesoft.com/manual?action=mancat&id=edb2sql&category=2 << they do work with oracle, Paradox and Microsoft sql server. >> Well, they may work in Paradox, but I'd be surprised if they worked in SQL Server and Oracle. You're just asking for trouble by mixing types like that, and it makes the SQL virtually unreadable since it is impossible to infer the types of the columns being compared against from the constants. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |