021 Tweaking MySQL Demo Data

TWEAKING MySQL DEMO DATA

Hi. We want to look at MySQL tweaking in the component area. You would open a component, go to settings, and there is MySQL tweak. What is this able to do is, if you have multiple versions of a component, 00:00:18 and partly you have demo that relates to a certain version of it and implementation of items, and in another version you don't want those items that you know included, we have this MySQL tweak area. Where you can actually, first you've select that specific view that you 00:00:43 want to tweak, and do note that you can only make use of this feature, if you're actually using this area where we actually add database connection between the view dummy data and view itself. Let me quickly show you what I mean. 00:01:07 I have opened field types which is one of component builders own views, and I have it connected to my database through this MySQL. I added yes. I selected table. I selected the field types in my database and basically just let it all be taken into the build file. 00:01:33

Tweaking Feature

Since you know that some of the versions that we distribute with component builder, doesn't have all the field types in it. It's a limited to only a certain few field types. So to show you how that was done, I will go back to tweaking feature. I have component builder open, and if I go to settings, 00:01:57 If I go to this tweak feature. You would see that I have added values here and certain of them like custom admin, I have set it to no, don't include the add MySQL(to view table) if set in the view. 00:02:19 If in the view, if you have the MySQL selected, you can through this(Add MySQL) feature control which items actual ids should be included. Like in the admin view, I'm only including these two ids(33,42) from my database. So it's the ids in the admin view table. I'm also saying that it's ID Based. You have the feature of 00:02:46 including all.

ID Based

And then you have 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 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 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 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 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.