-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDB Loader: fix ignored schema in metadata queries #178
Labels
Milestone
Comments
stdfalse
added a commit
that referenced
this issue
Mar 19, 2020
stdfalse
added a commit
that referenced
this issue
Mar 19, 2020
stdfalse
added a commit
that referenced
this issue
Mar 19, 2020
chuwy
pushed a commit
that referenced
this issue
Mar 19, 2020
chuwy
pushed a commit
that referenced
this issue
Jul 13, 2020
chuwy
pushed a commit
that referenced
this issue
Oct 23, 2020
chuwy
pushed a commit
that referenced
this issue
Oct 29, 2020
chuwy
pushed a commit
that referenced
this issue
Nov 25, 2020
chuwy
changed the title
Loader: fix ignored schema in metadata queries
RDB Loader: fix ignored schema in metadata queries
Nov 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
snowplow-rdb-loader/src/main/scala/com/snowplowanalytics/snowplow/rdbloader/db/Migration.scala
Line 58 in 1c977c4
Above statement supposed to make sure that next query is specific to one schema, but apparently it doesn't work. If user has two tables with same name in different schemas the
SELECT obj_description(oid)
will return two rows.The text was updated successfully, but these errors were encountered: