Unable to use table with schema name about node-rate-limiter-flexible

[paulsc54]

Ok great.

Certainly, I just need to carve out some time, and I'll get to work on it.

Thanks! I'll keep you posted

[animir]

@paulsc54 Hi, thanks for the bug report.
I am not quite familiar with how postgres works with database and table names.
Would separate dbName option be helpful here? In this case it could be part of query like this ${dbName}.${tableName}.
Could you help with defining the right approach for postgres? Thanks.

[paulsc54]

Double quotes are used to indicate identifiers within the database (tables, column names, roles, etc.). Therefore schema and database names have to be used as distinct identifiers. To enhance clarity, consider introducing a new parameter, schemaName, and employing it in this manner: ${schemaName}.${tableName}. (btw the parameter could be optional as by default postgres will target the public schema).

Regarding the dbName you referenced, its role doesn't extend to becoming a part of the query. Once the connection is established with the driver, the accessed database is implicit. Hence, our focus remains on specifying the schema and table.

[animir]

@paulsc54 Ok, thank you.
We should introduce new parameter schemaName, so it would be clear for postgres users.
As a temporary fix you can downgrade the package to version 3.0.0.

Would you be able to make this fix?

[paulsc54]

Just created #227.
I ran some tests on my local setup with Postgres, and everything appears to be in good shape.

Just make a few tweaks—nothing too extensive. That should get the job done.

[animir]

@paulsc54 Thank you!
I merged the PR.

The new version 3.0.2 published.

[paulsc54]

Amazing. Thank you!