Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why are these important, what effect do they have on the database at hand?
Isn’t the “schema” already decided at that point, as it exists in the database?
What exactly is a “catalog”? What kind of variable/input is the JPA catalog field expecting? Also, same question for the “schema” field.
Catalogs and schemas are “namespaces” that you define on the server side of the database. Some databases contains schemas, some contains catalogs, and some contains both. When logging in with a specific user, some databases defaults the schema/catalog to the user’s namespace, causing the table to not be visible to other users, thus, causing the need to use a “common” namespace. So, depending on the database you are using to back your data, you might want to ignore those settings.
For MySQL, you might want to ignore those settings. This is because the “database” part of the JDBC URL (the one after the last slash) points to the database name, which is semantically identical to schema (for MySQL).