Schema normalization rules no longer seem to have a limit to prevent infinite loops
See original GitHub issueThis feature in previous versions of Slate was really helpful, but in 0.42.x it doesn’t seem to be there; at least I’m not seeing it.
Error: A schema rule could not be normalized after sufficient iterations. This is usually due to a
rule.normalizeor
plugin.normalizeNode function of a schema being incorrectly written, causing an infinite loop.
I’ve been waiting to hit the maximum callstack while debugging some normalization rules and it made me realize how much I appreciated that failsafe. Was this intentionally removed, or did I break something?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Chapter 12 Normalization – Database Design – 2nd Edition
Normalization theory defines six normal forms (NF). Each normal form involves a set of dependency properties that a schema must satisfy and each...
Read more >Maybe Normalizing Isn't Normal - Coding Horror
Normalization certainly delivers in terms of limiting duplication. Every entity is represented once, and only once -- so there's almost no risk ...
Read more >When is a good time to break normalization rules?
All rules were meant to be broken, and if you have a piece of data in maybe 2 places that are very commonly...
Read more >Chapter 3. Data, Tables, and Database Design - O'Reilly
THE FIX: Normalizing basically means organizing data to reduce redundancy. As the esteemed Webopedia ( http://www.pcwebopedia.com ) pithily puts it, it involves ...
Read more >Relational Database Normalization Process
As mention before, relational database theorists have developed a series of guidelines for ensuring that databases are normalized.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just decreased to
100
so hopefully that helps.I think your point is good though that
1000
is too high to be useful so let’s keep this open til we fix it.