Updated 021 Tweaking MySQL Demo Data (markdown)

Amigo 2019-06-24 09:43:34 +02:00
parent 82678551fe
commit b0a16e510d
1 changed files with 1 additions and 3 deletions

@ -14,6 +14,4 @@ Some of the versions that are distributed with Component Builder, does not have
### ID Based
It is a function that is used to indicate what is needed. If 'ids' between let say 1 and 50 are used, then this arrow notation with an equals open bracket there(=>) can be used, to notate that between 1 and 500, you want to add. [00:03:15](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m15s)
Here it says:(See video) 1,2,3,4or1=>4 a comma is placed and then 20, then another comma and then 40=>90, so you can in the same comma delimited list, add this notation to show that 1 to 4 need to be included, immediately after it add 20 and all that ids will be grabbed. [00:03:41](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m41s) In fact it eliminate any other ids and only use the ones that has been notated. Here is another example of using 1,4,23,199 ; it goes on from 597=>604,682=>684.(See video) [00:04:08](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m08s) It is in the same comma delimited list, it is made id based, and include these by clicking 'yes'. That is what it can be used for. So if dummy data or example data has not been included in the component build structure, then this area is really redundant and it is not necessary to use it at all. [00:04:46](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m46s) Ignore it if there isn't any data selected. That is a tweaking feature in Component Builder's component area that helps with the management of dummy data between versions in your applications.
It is a function that is used to indicate what is needed here(See video). If 'ids' between let say 1 and 50 are used, then this arrow notation with an equals open bracket there(=>) can be used, to notate that between 1 and 500, you want to add. [00:03:15](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m15s) Here it says:(See video) 1,2,3,4or1=>4 a comma is placed and then 20, then another comma and then 40=>90, so you can in the same comma delimited list, add this notation to show that 1 to 4 need to be included, immediately after it add 20 and all that ids will be grabbed. [00:03:41](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m41s) In fact it eliminate any other ids and only use the ones that has been notated. Here is another example of using 1,4,23,199 ; it goes on from 597=>604,682=>684.(See video) [00:04:08](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m08s) It is in the same comma delimited list, it is made id based, and include these by clicking 'yes'. That is what it can be used for. So if dummy data or example data has not been included in the component build structure, then this area is redundant and it is not necessary to use it at all. [00:04:46](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m46s) Ignore it if there isn't any data selected. That is a tweaking feature in Component Builder's component area that helps with the management of dummy data between versions in your applications.