Finance | Project Operations, Human Resources, ...

What is exception error for failed sql query ?

(0) Share

Report

Posted on by VoltesDev

Hi guys,

When running my code that has a SQL query, such as this :

select firstonly SalesId from custInvoiceJourLoc where custInvoiceJourLoc.InvoiceId == conPeek(TempInvoices,1)
join firstonly DefaultDimension
from saleslineloc order by RecId
where salesLineLoc.SalesId == custInvoiceJourLoc.SalesId;

Often I'm hit error and error comes with this message :

I know what is the error, but may I know what Exception error we can use for this ? Is there any special Exception error for failed Sql query ?

Thanks,

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

GirishS 27,827 Moderator on at

Like (0)

Report

Hi VoltesDev,

I guess its belongs to exception of type NullReferenceException.

Thanks,

Girish S.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,801 Most Valuable Professional on at

Like (1)

Report
This is not a exception related to queries. It's object about object references in the application tier. It happens when you're trying (for example) to call a method on a reference that don't refer to any object at all.

For instance:

Args args; // The variable is empty. args.parm(); // We're trying to call parm() method of no object, which isn't possible to do.

It's System.NullReferenceException, but you normally shouldn't try to catch it. Instead, you should prevent the exception from occuring by fixing the bug in code.

Was this reply helpful? Yes No
Suggested answer

Mohit Rampal 12,565 Moderator on at

Like (0)

Report

Hi,I think this error will occur when container is null, so better to create a variable for InvoiceId and map conPeek(TempInvoices,1) in that variable. move your select statement in If condition that it should run only if InvoiceId has a value.

Was this reply helpful? Yes No
VoltesDev on at

Like (0)

Report

Hi all,

Yes, all the reason are correct. It is because the container is null. The plan is to catch it, and I will have an insert to ErrorLog procedure. Is there a reason why there is no exception for this ? instead we should fix the bug or make an IF condition to run when it is not null ?

Thanks,

Was this reply helpful? Yes No
Martin Dráb 237,801 Most Valuable Professional on at

Like (0)

Report

What do you mean by "why there is no exception for this"? Isn't the whole thread about this exception?

But it's just the last resort; you shouldn't get into this situation. Also, you see that this generic exception tells you nothing about the actual cause, therefore it's difficult to debug. Even if you log it, it tells you nothing more than that you have a bug in code.

Check if you have values to work with and if not, either skip the logic or throw an error explaining the problem.

Was this reply helpful? Yes No