Skip to content

Conversation

JoelJuntunen
Copy link

resolves #32

Description

This change fixes the issue where the Teradata environment operates in a mode that is not case sensitive and it is causing compilation errors for ambiguous schema names.

Note: This is a very crude implementation and suggestions are very welcome.

Checklist

  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md with information about my change

@JoelJuntunen JoelJuntunen closed this by deleting the head repository Aug 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Case Sensitivity in Schemas
2 participants