Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add option to use schema names in the actual queries instead of search_path changes

See original GitHub issue

e.g. DROP TABLE foo.bar instead of setting the search path to foo and then DROP TABLE bar.

Issue Analytics

State:
Created 8 years ago
Reactions:1
Comments:8

Top GitHub Comments

1reaction

jflambertcommented, Jul 10, 2018

@jonnio Does your fork solve the PostgreSQL 10 sequence issue #225 ?

0reactions

elidoriocommented, Jul 17, 2018

Excuse me, Can you pass me the path of the compiled jar of your fork?

Top Results From Across the Web

Documentation: 15: 5.9. Schemas - PostgreSQL

The first schema named in the search path is called the current schema. Aside from being the first schema searched, it is also...

Demystifying Schemas & search_path through Examples

This guide shows how to use PostgreSQL schemas with multiple users in your database. It also demonstrates the issues highlighted by ...

Incorrect schema name in the search path is called ... - GitHub

Create a new postgreSQL database with schemas: public (default schema), lookup. ... The following SQL should be in the "lookup" schema search path....

How does the search_path influence identifier resolution and ...

Instead of modifying the scripts, I want to set the database create tables in a specific schema by default - when they have...

Using search_path to target connections and aggregators

Note that the schema names match your Steampipe connection names: .inspect. The schemas, in turn, contain the foreign tables that you write queries...