Servoy Forum

It looks like you are right Adrian.

I checked my situation and I also see INSERTS but not the UPDATES

Hi martin,

Sorry for the late reply.

martinh wrote:

ROCLASI wrote:Robert,

Do you mean with that?

Databaseservername A connects to jdbc:jtds:sqlserver://SERVOY/example_data
Databaseservername B connects also to jdbc:jtds:sqlserver://SERVOY/example_data

In that case, this is not the case, because Servoy doesn't allow me (never had)

That's what I meant yes. This was still allowed in pre 3.5 versions (or was it pre 3.1).

martinh wrote:It looks like you are right Adrian.

I checked my situation and I also see INSERTS but not the UPDATES

Martin/Adrian,
Do you see the same issue between rich clients and web clients as well?

ROCLASI wrote:
Martin/Adrian,
Do you see the same issue between rich clients and web clients as well?

Hi Robert,

The same issue between web and smart clients. I made a test.

Changing an existing record and adding a new record in smart client
I see the new record in webclient, but not changes of the existing one.

When I restart the webclient, I see the changed value too.

Hi Martin,

Since you made a test can you also test between rich-client/rich-client and web-client/web-client?

Hi Robert,

Rich/Rich client same issue!

I started smart client on 2 different computers

I changed some description and I added a related record

When reselect the changed record, I don't see the change I made in description, but I do see the added record
Also when I delete a child record and I reselect the parent, the child record is not shown anymore

I made also test to delete the parent record

When the parent is delete on computer A I can still walk through the foundset on computer B and I see a record that has already been deleted
I can even still change that record!

On computer B I have 7 records and on computer A I still have 8 records

I can even add a new child record on the deleted record on computer A without errors
And in my database I still see 7 parent records.


BUT ....

I see in my database that a child record was added.
So now I have a child record without a parent in my database

So this looks to be a very serious problem!

Please file a case in our support system with a sample solution in which this can be reproduced + description how to reproduce it.

Paul

martinh wrote:Rich/Rich client same issue!

[snip]

So this looks to be a very serious problem!

That really sounds like one .

martinh wrote:I see in my database that a child record was added.
So now I have a child record without a parent in my database

That would have never happened when you would have put the referential integrity checks (foreign key constraints) not (only) in the application layer but in the database layer where it belongs. But that is another discussion altogether.


But please do what Paul is asking and file this test in the support system.

and please do post more info as you uncover it here, this is an important thread some of us are following, thanks!!

kazar

I submitted a case 223009 with a sample solution reproducing aspects of this problem on 6/30. The sample solution showed a foundset based on global relation failing to be updated correctly when a record was modified. This was all local in the same SC/WC, no batch process involved. The status of the case is still 'new' so I don't think it's been looked at yet. I've emailed Jan Blok and Paul Bakker asking that it be looked at soon. Thanks.

Update - I have just uploaded to case 22452 a sample solution which reproduces the problem exactly. It shows the server failing to broadcast updates a client-based foundset that is based on a global relation as records are modified by a batch process. Hopefully this will help Servoy resolve the problem.

Just received word from Servoy Support that this issue is fixed in release 5, beta 2. Here is an excerpt from the bug resolution report:

We have added support now for related foundsets to update when records are updated by another client.
This was working already, but only in the case that the client had loaded the record, since the new version it also works if the client has not loaded the record.

I'm not sure I'll have a chance to test this fix in the beta release anytime soon but perhaps someone else following this thread can test it and let us know their results.

Thank you Servoy Support for addressing this problem.