Connection loss or db name when extending pREST

[crgimenes]

I'm extending pREST and using config.PrestConf.Adapter.* to directly manipulate the database.

If someone happens to send an incorrect URL to the server, such as: http://example.com/nondb/public/tablename (with a database that doesn't exist) the server tries to open the db, fails and returns the error as expected but it loses the old connection or database name. Then no direct SQL statement will work anymore.

If I send a valid URL the pREST reconnects to the database and then everything works again.

[arxdsilva]

@crgimenes this should be fixed by version v1.1.0, could you update to v1.1.2 and retry?

I'll close this and if it doesnt work feel free to reopen