[fpc-pascal] Troubles with SQLDBRESTBridge

[Sven Barth]

Am 23.06.2019 um 11:31 schrieb Michael Van Canneyt:
>
>
> On Sun, 23 Jun 2019, Sven Barth via fpc-pascal wrote:
>
>>>> Okay, independently of whether the REST module is the optimal 
>>>> solution or not, it should work, right? (and shouldn't the Wiki 
>>>> entry then mention the advantages/disadvantages of the two 
>>>> approaches? Cause when looking at the SQLDB REST module I thought 
>>>> "yay, less stuff to configure" and rolled with that)
>>>
>>> What exactly is less to configure ? :)
>>
>> Looking at the Wiki again I was fooled by the Datamodule having 8 
>> bullet points, the SQLDBRestModule having 5, but the later simply 
>> shortening stuff with point five... So yeah... not really less to 
>> configure... My fault. ^^'
>
> It's OK. I will try to document it a little better.

Would probably be best, thank you. :)
>
>> By the way: I sometimes get a EStreamError *after* all data had been 
>> sent to the client. I have not yet found a reproducible way for this...
>
> Please make sure  you have the latest version of everything: I had this a
> couple of times in case of an error. I fixed all occurrences, I hope.
>
> But if you find additional cases: let me know.

Yes, I was using the latest version. But I'll try to find a 
reproduceable case. :)

>>
>>>> - localhost:8080/metadata works
>>>> - localhost:8080/users returns "INVALID RESOURCE"
>>>
>>> Because it has rdoConnectionInURL set, and so you must do
>>> localhost:8080/expenses/users
>>
>> Ahhhhhh! Hadn't seen that this option is active... Okay, then it 
>> indeed works as expected, both with and without rdoConnectionInURL.
>>
>> By the way: I noticed a slight annoyance, but I don't know whether 
>> one can really do something about that: When I set rdoConnectionInURL 
>> to False inside the object inspector it turns on again, because 
>> rdoConnectionResource is set. Took me a moment to look at the source 
>> code to see that I need to disable rdoConnectionResource first. Don't 
>> know what a better solution would be...
>
> Funny you mention this, I was fooled myself yesterday, I also had to 
> look in
> the sources :(
>
> One way would be to disable rdoConnectionResource if you disable
> rdoConnectionInURL. I will add this.

But wouldn't that lead to an analogous problem with 
rdoConnectionResource if rdoConnectionInURL is not set?

Regards,
Sven