lack of schemaName support

[snovak7]

I was digging through, and I can't query anything that has schema/database prefix.

[ArsalanDotMe]

I'm having the same issue. You can fix this issue by bypassing utils.escapeName in sequel/select.js.

[sailsbot]

Thanks for posting, @snovak7. I'm a repo bot-- nice to meet you!

It has been 30 days since there have been any updates or new comments on this page. If this issue has been resolved, feel free to disregard the rest of this message. On the other hand, if you are still waiting on a patch, please:

• review our contribution guide to make sure this submission meets our criteria (only verified bugs with documented features, please; no questions, commentary, or bug reports about undocumented features or unofficial plugins)
• create a new issue with the latest information, including updated version details with error messages, failing tests, and a link back to the original issue. This allows GitHub to automatically create a back-reference for future visitors arriving from search engines.

Thanks so much for your help!

[dzuluaga]

Did you guys figure this out? It still writes to public schema, regardless of the schemaName set to the model. Am I missing anything? I'm looking at this http://stackoverflow.com/questions/24380902/database-schema-with-sails-js-and-sails-postgresql

[ArsalanDotMe]

I only had to read from a custom schema table so I bypassed this issue by
creating a view on public schema.

On Tue, Nov 3, 2015, 11:50 AM Diego Zuluaga notifications@github.com
wrote:

Did you guys figure this out? It still writes to public schema, regardless
of the schemaName set to the model. Am I missing anything? I'm looking at
this
http://stackoverflow.com/questions/24380902/database-schema-with-sails-js-and-sails-postgresql

—
Reply to this email directly or view it on GitHub
#60 (comment)
.

[dzuluaga]

Yes. Weird. My use case is slightly different. I'm trying to save a record, but still a pretty common one. I liked Waterline, but I don't know how to tell my customer you can only use public schema for storing data, which seems dangerous. To replicate the issue, you can find the code here: https://github.com/balderdashy/sails-postgresql/issues/207

[ArsalanDotMe]

When I had the issue, I tried going through the code to find the issue. While I wasn't able to debug the real problem, I was able to find a hack that works.
Basically, in waterline-sequel, it wraps table name in quotation marks. If it's possible for you, you can edit the code to not wrap the table name with quotation marks and in your model, use the table name as yourschema.yourtablename instead of just yourtablename.
Its still an ugly hack but can get you going for the time-being.

[dzuluaga]

Yeah. I just tried but it fails. It though created a table in public schema with name testmyapischema.user, instead of creating the table under testmyapischema. The model was set as: tableName : 'testmyapischema.user'. Thanks!