| Key: |
SEQUOIA-837
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Jeff Mesnil
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
For Sequoia 3.0, we want to have a more tunable macro handler (only for random and date macros) so that Sequoia can adapt to the macros specific to a DB types (random/date macros for MySQL are slightly different from macros for PostgreSQL).
In the current HEAD, this list of macros is defined in the LoadBalancer section of the VDB XML file.
However, it is less that satisfactory since the list of macros for a given DB must be repeated in each and every VDB XML files which uses a given DB type.
We should remove the macros definition from the VDB XML (and its DTD) and make it possible in Sequoia to configure this macro list for each DB type outside of VDB definition so that the usage of macros will be transparent to Sequoia users in most cases.
The proposed implementation is to have a simple properties file for each DB types where we will list the macros for the given DB type.
Then, when loading a VDB XML file, for each new database backend, we will use the DB prefix of its JDBC url (e.g. mysql) to load the corresponding macro list and add these macros to the VDB's LoadBalancer.
If we can't load a corresponding properties file, the DatabaseBackend won't be created and the VDB won't be loaded.
The only caveat of this approach is that the users will have to create a properties file for each DB type they use. However with the help of the Sequoia community, it should be possible to include these files for most of the DB used by the community directly in Sequoia CVS.
|
|
There are no comments yet on this issue.
|
| |
|
|
Make macro list configurable per DB types
