-
Notifications
You must be signed in to change notification settings - Fork 55
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
Multi db access #1437
Open
dgrothaus-mc
wants to merge
9
commits into
yakamara:master
Choose a base branch
from
mediaconstructor:multi_db_access
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Multi db access #1437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alxndr-w
reviewed
Apr 2, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spricht etwas gegen den PR? Ich fände es klasse, wenn DB[n] in YForm zugänglich wäre.
dgrothaus-mc
force-pushed
the
multi_db_access
branch
from
April 10, 2024 08:28
2d977c5
to
a5cc06b
Compare
Mirror the PHP and Redaxo core requirements from package.yml to composer.json.
Don't throw an exception when no related table or field is set.
Let yform track the db_id of a table.
Allow to set the database id for yform by passing the parameter $param['db_id'] to the constructor or by calling the method `setDatabaseId()`
Use the db_id from yform. Pass the db_id to rex_sql calls and add a getter to get the database id for managed tables.
All calls that are made by classes using yform are now aware of db_id and use the proper ID when querying the database.
Editing and migrating tables make use of db_id.
dgrothaus-mc
force-pushed
the
multi_db_access
branch
from
April 10, 2024 08:33
a5cc06b
to
d5e4a93
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ich habe den bereits vorhandenen PR #1147 aufgegriffen und sowohl yform als auch den Table Manager entsprechend angepasst. Migrieren und Editieren von Daten funktioniert soweit stabil. Die gemachten Änderungen sind intern jetzt drei Wochen lang in einem Projekt getestet worden.
So lange in der Redaxo
config.yml
nur eine Datenbankverbindung eingerichtet ist, ändert sich weder etwas am Verhalten noch am Aussehen. Die zusätzlichen Felder und Funktionen werden erst dann sichtbar, wenn mehr als eine Datenbankverbindung eingerichtet ist.