Final answer:
According to advocates of the CODASYL model, the relational model is criticized for being too mathematical, having set-oriented queries that complicate certain operations, not accommodating record-at-a-time processing well, and being less efficient than CODASYL databases in some use cases.
Step-by-step explanation:
The debate between different database models often revolves around their ease of use, efficiency, and the way data is processed and accessed. Advocates of the CODASYL model have criticized the relational model, which was introduced by E.F. Codd in 1970, for a series of supposed disadvantages.
Too Mathematical: The relational model is based on set theory and predicate logic, which some argue is too theoretical and abstract, making it difficult for practitioners who are not well-versed in these mathematical concepts to grasp.
Set-oriented Queries: CODASYL proponents claim that the set-oriented nature of queries in the relational model can be challenging when more traditional, procedural methods of data retrieval are required or when performance tuning is necessary.
Record-at-a-time Processing: Another criticism is that application systems often need to process data one record at a time, which proponents of CODASYL argue is handled better by their model. They suggest that the relational model's set-based processing is not always the most effective approach for transactional systems that require frequent, instantaneous updates to data.
Efficiency: Efficiency is another point of contention. CODASYL supporters maintain that their model's approach to database design and access can outperform the relational model in certain scenarios, leading to faster and more predictable performance.