For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
TAG using JSON value might be more flexible.
This would then allow template based code generators (eg ) to automatically identify which tables need to be combined together to create a specific Transactional API (XAPI). (eg an API that must work with >1 tables)
MK
Tags for table columns, constraints, etc. would also be useful.
TAG using JSON value might be more flexible.This would then allow template based code generators (eg ) to automatically identify which tables need to be combined together to create a specific Transactional API (XAPI). (eg an API that must work with >1 tables)MK
Great Mike!It really should be done with JSON syntax. It allows to create different kinds of tags in a single 'tag column', like: [...]TAGS ('{Use:Transactional, SensitiveData:false, Version1.0:MatheusDBA, Version2.0:AnotherDBA}');
Or even tags hierarchies/subtypes... Anyway, it's way more flexible.Thanks for this insight!
Exactly... I just used some kind of objects for this example... but I believe it can apply for any king of object, including schemas... like (using Mike's contribution): CREATE USER USER_EXAMPLE TAGS ('{Use:AdHocReports, Accountable:InternalBusinessTeam}');
This would definitely be useful.