From 82678551fe0bdeea0e62c9a2e5507530a11ebda4 Mon Sep 17 00:00:00 2001 From: Amigo <49749100+aamigo@users.noreply.github.com> Date: Mon, 24 Jun 2019 09:36:05 +0200 Subject: [PATCH] Updated 021 Tweaking MySQL Demo Data (markdown) --- 021-Tweaking-MySQL-Demo-Data.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/021-Tweaking-MySQL-Demo-Data.md b/021-Tweaking-MySQL-Demo-Data.md index eb1afea..bacecf5 100644 --- a/021-Tweaking-MySQL-Demo-Data.md +++ b/021-Tweaking-MySQL-Demo-Data.md @@ -10,8 +10,10 @@ Open a component(in this instance 'Editting a component'), go to 'settings', and ### Tweaking Feature -Some of the versions that are distributed with Component Builder, does not have all the field types in it. It's a limited to only a certain few field types. To explain what has been done: Return to the tweaking feature. with Component Builder open, go to settings. [00:01:57](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m57s) In this tweak feature, added values may be seen and certain of them like Custom Admin, has been set to 'no', do not include the add MySQL(to view table) if set in the view. [00:02:19](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m19s) If 'MySQL' were selected in the view, then through this(Add MySQL) feature it can be controlled which item's actual 'ids' should be included. Like in the Admin View, only these two 'ids'(33,42) have been included from the database. It is the 'ids' in the Admin View table. It is ID based. There is the feature of including all.[00:02:46](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m46s) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<, +Some of the versions that are distributed with Component Builder, does not have all the field types in it. It's a limited to only a certain few field types. To explain what has been done: Return to the tweaking feature. with Component Builder open, go to settings. [00:01:57](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m57s) In this tweak feature, added values may be seen and certain of them like Custom Admin, has been set to 'no', do not include the add MySQL(to view table) if set in the view. [00:02:19](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m19s) If 'MySQL' were selected in the view, then through this(Add MySQL) feature it can be controlled which item's actual 'ids' should be included. Like in the Admin View, only these two 'ids'(33,42) have been included from the database. It is the 'ids' in the Admin View table. It is ID based. There is the feature of including all.[00:02:46](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m46s) ### ID Based -So it's a way to say what you want here. You can also if you are using ids between let say 1 and 50, then you can use this arrow notation with an equals open bracket there(=>), to know take between 1 and 500, you want to add. [00:03:15](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m15s) And you can actually do it quite simply, over here I'm explaining it nicely, it says 1,2,3,4or1=>4 you can put a comma and then 20, then another comma and then 40=>90, so you can in the same comma delimited list. You can add this notation [00:03:41](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m41s) to show that we need to include 1 to 4. And immediately after it add 20 and we will grab all that ids. In fact it illuminate any other ids and only use the ones that you have actually notated. Here is another good example of using 1,4,23,199 [00:04:08](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m08s) so it goes on in here from 597=>604,682=>684. It's in the same comma delimited list, and we saying is it's id based, and we say include these(yes). That is partly what I'm having, why this is here, what it can be used for. So if you're not including dummy data or example data in your component build structure, then this area is really redundant and you don't need to even use it all. [00:04:46](https://www.youtube.com/watch?v=wkSLZUEN-RE&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m46s) You can just ignore it system, ignores it as if it doesn't exist if there isn't any data selected. Well that is some tweaking feature in component builders component area that helps you manage your dummy data between versions in your applications. +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.