the code contains hard-coded references to the public schema

[olliebun]

Hi there! Here at GreenSync we're big fans of que-rb.

We're working on a complex system where we want to use different postgres database schemas to manage different components of the system within a single database.

Unfortunately, it looks like there are a few hard-coded references to public. in the code:

https://github.com/que-rb/que/search?q=public.

This means that even if we pass que-rb a connection that has a schema other than default configured, there are a mixture of references to tables with and without the hard-coded public. prefix - so it just won't work.

If you're open to addressing this, we'd be happy to open a PR.

Some possible approaches:

• support telling que what schema to prefix on the tables
• never prefix the tables & rely on whatever schema has been set on the connection passed to que

Thoughts?

[lewispb]

Possibly related.. we'd like to use Que in tandem with Rails multi-db support. Therefore specifying a different base class (instead of ActiveRecord::Base) as the base class for our Que tables.