Skip to content
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

Extend hybrid model to include sql #680

Closed
iromli opened this issue Jan 24, 2022 · 2 comments
Closed

Extend hybrid model to include sql #680

iromli opened this issue Jan 24, 2022 · 2 comments

Comments

@iromli
Copy link
Contributor

iromli commented Jan 24, 2022

Currently, the hybrid model is exclusive for LDAP and Couchbase. A new feature in the ORM layer allows alias support for SQL to separate mappings.
Hence if the user-specified RDBMS the hybrid model should take into account the alias support rather than just the cross of Couchbase and LDAP.

Sample of jans-hybrid.properties when persistence type is hybrid and of type SQL.

storages: sql, sql.token
storage.default: sql
storage.sql.token.mapping: cache, tokens, sessions

The above snippet means that cache tokens, and sessions are in a separate database in SQL. This also means two conf property files will be needed, jans-sql.properties and jans-sql.token.properties.

This is very similar to couchbases mapping. Instead of CN_SQL_DB_NAME we should probably use a prefix style CN_SQL_DB_NAME_PREFIX

@iromli iromli added kind-enhancement Issue or PR is an enhancement to an existing functionality comp-jans-pycloudlib labels Jan 24, 2022
@iromli iromli changed the title Extend hybrid model to sql Extend hybrid model to include sql Jan 24, 2022
@iromli iromli added kind-feature Issue or PR is a new feature request and removed kind-enhancement Issue or PR is an enhancement to an existing functionality labels Jan 24, 2022
@iromli
Copy link
Contributor Author

iromli commented Jun 6, 2022

The above snippet means that cache tokens, and sessions are in a separate database in SQL. This also means two conf property files will be needed, jans-sql.properties and jans-sql.token.properties.

This is very similar to couchbases mapping. Instead of CN_SQL_DB_NAME we should probably use a prefix style CN_SQL_DB_NAME_PREFIX

This would be tracked in separate GH issue (if feature is really still needed).

@iromli
Copy link
Contributor Author

iromli commented Jun 10, 2022

Closing this issue. The alias support will be tracked in #1541

@iromli iromli closed this as completed Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment