Add/Update failed. How do I foind out why

h.hasenack · 2012-12-14 20:46:11

I can find out using my debugger, but it would be so much better to have an 'GetLastError' solution, or maybe have an exception at client side raised that contains info about WHY the update failed.

Errors can haCOuld be e.g.
* the database rejected (key violation, invalid data etc) the update from the mOrmot
* mormot rejected the data
* communication failure/dropout

Currently it is quite hard (clienty side) to find out .

SUggestion:

find a way to catch/hold on to the "last" server side exception / exception message, and send it over to the client, either directly with the reply (not preferred due to bandwith considerations) or (preferably) in for form of a GetLastMotmotError:UTF8string / raiseLastMormotError solution that queries the server for the last exception/error info.

Hans

ab · 2012-12-15 11:05:48

Good idea.

I've added a task to the RoadMap:

Refactor the Client-Server error process, with better transmission of the error raised on server side to identify the cause of a failure on client side;

See http://synopse.info/fossil/wiki?name=RoadMap

h.hasenack · 2012-12-15 12:37:26

Gr8!

ab · 2013-01-24 08:55:51

Feature request raised again.
http://synopse.info/forum/viewtopic.php?id=1053

mpv · 2013-01-24 16:07:23

I also need this feature. For example in TSQLDBConnection.NewStatementPrepared database error go to nowhere. So it's impossible to get error message been raised on database level (only in log files). Aa solution may be add "var Err" to

function TSQLDBConnection.NewStatementPrepared(const aSQL: RawUTF8;
  ExpectResults: Boolean; var Err: RawUTF8): TSQLDBStatement;
begin
  try
    result := NewStatement;
    result.Prepare(aSQL,ExpectResults);
  except
    on E: Exception do
      FreeAndNil(result);
      Err := StringToUTF8(E.Message)
  end;
end;

and push it up to NewThreadSafeStatementPrepared level?

ab · 2013-01-30 13:33:30

1. I've added TSQLRestClientURI.LastErrorCode/LastErrorMessage/LastErrorException properties, to retrieve additional information about remote URL() execution.
It will allow to retrieve the error on client side, as returned by the RESTful request.
See http://synopse.info/fossil/info/f2733cdb53

2. I've added RaiseExceptionOnError: boolean=false optional parameter to TSQLDBConnection.NewStatementPrepared() method, and TSQLDBConnection.LastErrorMessage and LastErrorException properties, to retrieve the error when NewStatementPrepared() returned nil.
This would help to better handle errors in SynDB* units, as mpv expected.
See http://synopse.info/fossil/info/5f4d9a1c8b

Feedback is welcome.

mpv · 2013-01-30 14:40:51

O! This is very good.

Roberto Schneiders · 2013-02-01 16:41:21

Thanks Arnaud.

I have some questions.

I just do not know when the server connection is working or not.

I have this code:

Client:= TSQLHttpClient.Create = ('127 .0.0.1 ', '888', Model);

Is there any way to test if a connection to the server is ok?

In the example that I put in this post http://synopse.info/forum/viewtopic.php?id=1053
There is still no solution for this, right?

ab · 2013-02-01 18:53:49

Just check the LastErrorException property if the method returned FALSE or 0 (meaning error): you should have a timeout exception here.

There is no such "ping" feature available, due to the nature of HTTP clients.

Roberto Schneiders · 2013-02-01 19:16:11

I just do not have the server started.

After this line

Client:= TSQLHttpClient.Create = ('127 .0.0.1 ', '888', Model);

the Client.LastErrorException is nil.

ab · 2013-02-01 20:49:13

TSQLHttpClient.Create() does not make any connection attempt.
You need to perform a remote RESTful command to connect.

I've just made a fix to TSQLHttpClientGeneric.InternalURI() method in order to raise an explicit exception on connection error.
See http://synopse.info/fossil/info/5721ad49cf

Now Client.ErrorMessage='Server not available (System Error. Code: 12029.)' for instance, with fLastErrorException=EOSError for TSQLHttpClientWinHTTP kind of connection.

So you can make such tests:

    Client := TSQLHttpClient.Create('localhost','888',Model);
    if not Client.SetUser('User','synopse') then begin
      ShowMessage(UTF8ToString(Client.LastErrorMessage));
      exit;
    end;

If you want just to test the connection, you can try the newly added TSQLRestClientURI.ServerTimeStampSynchronize method.
See http://synopse.info/fossil/info/900710ea17

Thanks for the feedback.

Junior/RO · 2013-02-01 20:57:46

Great! Good work. I was waiting for some code like this too

Last edited by Junior/RO (2013-02-01 20:58:09)

mORMot Open Source

#1 2012-12-14 20:46:11

Add/Update failed. How do I foind out why

#2 2012-12-15 11:05:48

Re: Add/Update failed. How do I foind out why

#3 2012-12-15 12:37:26

Re: Add/Update failed. How do I foind out why

#4 2013-01-24 08:55:51

Re: Add/Update failed. How do I foind out why

#5 2013-01-24 16:07:23

Re: Add/Update failed. How do I foind out why

#6 2013-01-30 13:33:30

Re: Add/Update failed. How do I foind out why

#7 2013-01-30 14:40:51

Re: Add/Update failed. How do I foind out why

#8 2013-02-01 16:41:21

Re: Add/Update failed. How do I foind out why

#9 2013-02-01 18:53:49

Re: Add/Update failed. How do I foind out why

#10 2013-02-01 19:16:11

Re: Add/Update failed. How do I foind out why

#11 2013-02-01 20:49:13

Re: Add/Update failed. How do I foind out why

#12 2013-02-01 20:57:46

Re: Add/Update failed. How do I foind out why

Board footer