Open
Description
Describe the solution you'd like
Current incremental multiline cards logic is the following:
SQL commands can be divided into: #card #incremental
Data Definition Language
Data Manipulation Language
Data Control Language
This creates 3 cards
SQL commands can be divided into: #card #incremental
?
Data Manipulation Language
Data Control Language
SQL commands can be divided into: #card #incremental
Data Definition Language
?
Data Control Language
SQL commands can be divided into: #card #incremental
Data Definition Language
Data Manipulation Language
?
This allows for learning a position of a unit of information in the context but doesn't allow for leaning the sequences of information (making the hashtag sorta ironic)
Describe how it will help your workflow
Adding #seq
hashtag on top of #card #incremental
SQL commands can be divided into: #card #incremental #seq
Data Definition Language
Data Manipulation Language
Data Control Language
to generate following cards
SQL commands can be divided into: #card #incremental #seq
?
-
-
SQL commands can be divided into: #card #incremental #seq
Data Definition Language
?
-
SQL commands can be divided into: #card #incremental #seq
Data Definition Language
Data Manipulation Language
?
This allows for learning any sequential data - algos, verb conjugations, etc