Firedac errors

[Midsoft UK]

Hi all

is there a way to get better error messages form FireDac ?

For example I have no way of knowing without trial and error which query the issue below refers to. I would have expected the query name in the message.

--------------------------

[FireDAC][Phys][FB]Dynamic SQL Error

SQL error code = -206

Column unknown

JOBNO

At line 2, column 7.

---------------------------

OK   

---------------------------

Thanks

[Jason (PN)]

How about adding something like this to the FDConnection event OnError?

I am hoping it fires on all exceptions that are generated via the connection.

 

procedure TForm2.FDConnection1Error(ASender, AInitiator: TObject; var

    AException: Exception);

begin

  if (AInitiator <> nil) then

    if AInitiator is Tcomponent then

      AException.Message:='Error: '+Tcomponent(AInitiator).Name+' threw a wobbly'+crlf+AException.message;

 

Jason Chapman

JAC2 Consultancy Limited

Mob: 07966211959

--
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/0864091e-8027-436b-8fae-e0d976e7fcfbn%40googlegroups.com.

[Tomasz Tyrakowski]

Apart from the answer posted earlier by Jason, if you run your
application from within the Embarcadero IDE, it stops whenever an
exception pops up, and you can check the full call stack and identify
the precise spot where the exception was raised (and the caller of that
routine, and the caller of the caller, etc., finally arriving at your
code that was the actual source of the problem). Setting a proper
breakpoint will allow you to inspect the exact query string that caused
the exception before it gets executed. So there's no "trial and error",
just use the debugger.
I use IBObjects to access the DB, which provide the query component name
in the error message, but it usually doesn't help much, as query objects
are often reused multiple times, and at the end of the day the debugger
is still the best option.

cheers
Tomasz
________________________________


Ta wiadomość zawiera poufne informacje przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.

[Karol Bieniaszewski]

First of all do not multipost– you have asked here as „better error messages”

And you got an answer from Mark Rotteveel.

 

I really do not understand your problem. You are the autor of the application?

If yes, simply add try except when you open some query.

e.g.:

 

fdquery1.SQL.Text:= ‘SELECT 1/0 FROM RDB$DATABASE’;

try

   fdquery1.open;

except

   on E: Exception do

      begin

         E.Message:= E.Message + sLineBreak + fdquery1.SQL.Text;

          Raise;

      end

end;  

 

you got full sql query text in error message.

You can also create procedure like FDOpen(FDQuery: TFDQuery) with above code to use it in avery places.

 

Regards,

Karol Bieniaszewski

--

[Midsoft UK]

Hi

I didn't know the two groups were connected so no idea it was cross posting. Google is big !

Your suggestion is what we have resorted to for now.  We are used to ADS always giving the component name in their errors and were interested to find out if Firedac could do the same

Andy

[fernande...@gmail.com]

I have converted from ADS to firebird/firedac, how are you running the SQL script. TFDQuery?

Does the query run in a DB editor?

Might be a problem with Field mapping to a component.

 

Regards

 

 

Flavius Fernandes

Founder |Solution & Software Architect

ERPSirius UK

https://www.erpsirius.co.uk/

https://www.linkedin.com/in/flavius-fernandes-50467b22/

To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/f80123c2-e2ef-4ab7-a525-d8a454d567e9n%40googlegroups.com.

[Midsoft UK]

Hi Falavious

You will notice that ADS shows errors like "AdsQuery1 error 5305, record locked..." or 7200 SQL error.

Yes we are using TFDQuery. Its no big deal if it doesn't do it now we know, we can handle it another way.

[Mark Rotteveel]

On 2021-07-08 15:25, Midsoft UK wrote:
> I didn't know the two groups were connected so no idea it was cross
> posting. Google is big !

Which two groups? You posted both to the firebird-support Google Group.

Mark

[Midsoft UK]

Ah, I'd thought I'd selected the delphi FireDac group. My mistake.

[Midsoft UK]

Doesn't look like there is one !

[Jason (PN)]

Hi,

 

I also note that if you create an application level inspection handler (Search for TApplication.OnException I think), you can then inspect the actual exception object raised.

 

If e is EFDDBEngineException then

  EFDDBEngineException(e).FDObName…..

 

Looks like they have anticipated this and made it pretty easy to add code in one place.

 

 

Jason Chapman

JAC2 Consultancy Limited

Mob: 07966211959

ukDevGroup organiser – UK Based Delphi and a hundred other things all wrapped up in a friendly monthly meeting www.ukdevgroup.co.uk

To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/047e3e89-e0a5-4f83-85ad-10f10347e75cn%40googlegroups.com.

[Midsoft UK]

Well found :) I had to remove the field to force the error.

 except

  on E: EFDDBEngineException do

   begin

     //showmessage(E.Message + ' dmData.FDQPopHead.Open');

     showmessage(E.Message + '  '+E.FDObjName) ;

   end;

 end;

[Window Title]

Servtrak

[Content]

[FireDAC][Phys][FB]Dynamic SQL Error

SQL error code = -206

Column unknown

JOBNO

At line 2, column 7  dmData.FDQPopHead

[OK]

[Ariel Álvarez]

http://docwiki.appmethod.com/appmethod/1.13/topics/en/Handling_Errors_(FireDAC)

Regards,

Ariel

To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/77252572-22af-4aea-b257-d9792c69f656n%40googlegroups.com.