If Only CodeGear would eat their own dogfood ...



  • And use Interbase instead of SQL Server ....

     



  • Codegear? 

    Dogfood?

    Interbase?

    What?



  • @dhromed said:

    Codegear? 

    Dogfood?

    Interbase?

    What?

     

    Codegear is the new company that has been separated from Borland; Codegear makes Delphi, JBuilder etc. and also Interbase, "a high-performance, cross-platform, Unicode, SQL 92 compliant database".



  • @dhromed said:

    Codegear? 

    Dogfood?

    Interbase?

    What?

    Codegear=wholly-owned subsidiary of Borland (http://en.wikipedia.org/wiki/CodeGear)

    Dogfood=http://www.joelonsoftware.com/articles/fog0000000012.html (takes a while to get to the point, though)

    Interbase=database server made by Codegear (http://en.wikipedia.org/wiki/InterBase)

    What=Determiner; Noun modifier which indicates that the precise identity of the noun is unknown, and is requested (http://en.wiktionary.org/wiki/what)



    This answer brought to you courtesy of the open-source information community. 



  • Could it not be that the generic SqlException's reference to SQL Server is for Interbase? I don't know much about .NET, but that is a system level exception.



  • Nah, the stack trace points to SqlClient garbage, which is MS SQL-specific, if memory serves.



  • While I agree they should use their own products as much as possible (and in fact they do use InterBase quite a bit for a number of things), in this case it was apparently a hard drive failure - so the particular database product would not have mattered.



  • Where'd you get a hard drive failure from that exception? Sounds like the database server is down...



  • @sootzoo said:

    Where'd you get a hard drive failure from that exception? Sounds like the database server is down...

    Actually, it's the generic "I'm not telling you exactly" SQL Server message. The database could be down. The database might not exist. Or, if memory serves, the specific object you're attempting to use won't let you. We get that every now and then when the DBAs do a restore of a database or refresh from another environment and forget to give our system accounts permissions.



  • @webzter said:

    @sootzoo said:

    Where'd you get a hard drive failure from that exception? Sounds like the database server is down...

    Actually, it's the generic "I'm not telling you exactly" SQL Server message. The database could be down. The database might not exist. Or, if memory serves, the specific object you're attempting to use won't let you. We get that every now and then when the DBAs do a restore of a database or refresh from another environment and forget to give our system accounts permissions.

    Or.. it is telling you exactly... You are describing a perfect condition for "Access is Denied". What better explanation would you hope for? The username and password that didn't work displayed on your screen?.

    Or it could be that the SQL Server specified in the web.config is not responding/non existant...

    Sounds like the error msg is right on the money to me...

     



  • @MasterPlanSoftware said:

    @webzter said:

    @sootzoo said:

    Where'd you get a hard drive failure from that exception? Sounds like the database server is down...

    Actually, it's the generic "I'm not telling you exactly" SQL Server message. The database could be down. The database might not exist. Or, if memory serves, the specific object you're attempting to use won't let you. We get that every now and then when the DBAs do a restore of a database or refresh from another environment and forget to give our system accounts permissions.

    Or.. it is telling you exactly... You are describing a perfect condition for "Access is Denied". What better explanation would you hope for? The username and password that didn't work displayed on your screen?.

    Or it could be that the SQL Server specified in the web.config is not responding/non existant...

    Sounds like the error msg is right on the money to me...

    I didn't say I cared. In fact, it's a great generic error to hide any security concerns.... but a more helpful error would be something like 'Access denied' or 'database does not exist'



  • The Real WTF here is that they're providing exceptions to their users instead of the generic "something didn't work" page that .NET will give you (or even better, an HTML page with pretty graphics!).

    And yes, SqlClient is the namespace used for connecting to MSSQL. If you wanted to connect to a non-Oracle/MSSQL server, you'd use System.Data.ODBC or System.Data.OleDB or even System.Data.Common.
     



  • @un.sined said:

    The Real WTF here is that they're providing exceptions to their users instead of the generic "something didn't work" page that .NET will give you (or even better, an HTML page with pretty graphics!).

    And yes, SqlClient is the namespace used for connecting to MSSQL. If you wanted to connect to a non-Oracle/MSSQL server, you'd use System.Data.ODBC or System.Data.OleDB or even System.Data.Common.
     

    CustomErrors=Off

    Most likely a .net newbie....


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.