JORGE MALDONADO wrote
> And so on. What I see is that it is not a good decision to set a key for
> every possibility because it will have an impact on performance due to
> index maintenance. What would be a good way to define indexes in a case
> like this?
For your specific case, and also more gen
I have a table with fields as follows:
* sag_id
* sag_header
* sag_comments
* sag_date
* sag_section_id (**)
* sag_artist_id (**)
* sag_author_id (**)
* sag_producer_id (**)
As you can see, fields mark with (**) are identifiers that reference
another table (catalog of sections, catalog of artists
