View Vs. Table

[LWSChad]

Hello;

Do views and tables have different performance characteristics?

Or, is their only purpose to provide multi-table data sets?

 

Consider these two scenarios:

 

tbl_1 -> fld_1  |  fld_2  |  fld_3  |  fld_4  |  fld_5  |  fld_6

 

frm_1 -> tbl_1.fld_3  |  tbl_1.fld_5

 

Will the following View save me data usage or speed up the call? (or do anything else)

 

view_1 -> tbl_1.fld_3  |  tbl_1.fld_5

 

----------------------------------------------------------------------------

 

frm_2 - tbl_1.fld_1  |  tbl_1.fld_2  |  tbl_1.fld_3  |  tbl_1.fld_4  |  tbl_1.fld_5  |  tbl_1.fld_6  

 

Will the following View slow down the call? (or do anything else)

 

view_2 - tbl_1.fld_1  |  tbl_1.fld_2  |  tbl_1.fld_3  |  tbl_1.fld_4  |  tbl_1.fld_5  |  tbl_1.fld_6  

 

 

THANKS

[jonathanr]

Hi Chad,

 

This is a very good question.

 

To answer the first part about data usage, there is no difference between using a table versus a view.

 

For the second part of your question, if you create a view based on a subset of your table, your view will be faster. For example, if you have a table with 40 fields and you create a view based on this table with only 10 fields, then your view will speed up the call.

 

Now, if you do a view with a join between 2 tables, it will be slightly slower than using a table by itself. Having said that, for most of the case it will be insignificant to the end users.

 

I hope this help.

 

Regards,

Jonathan

[LWSChad]

Cool, thanks for the explanation.

 

I use multiple datapages in many of my webpages, and every user interaction (up to 75 / hour / user) must process multiple auto-submitting datapages.

 

A tenth of a second per datapage load might add up... we'll see.

 

Thanks

[USMarine]

When is it best to create a "table" versus create a view of a table? What is a good rule to use as a gauge when considering whether to add more fields to an existing table and generate a smaller views  of that table (perhaps for a common inquiry or search results) or to create a separate table, bridge the two tables and display a filtered results in a view?

 

Just so that I can have a better understanding of when/why to do things, why is it better to go through the trouble of creating two tables and a filtered view of bits of info pulled from portions of each table, rather than put all the information into one table and define which bits of info. you'd like displayed in a filtered view of one table?

[NailDyanC]

Hi,

Just want to add to the previous comment above, the first step in creating a web application is to create its data tables. Tables hold your data. You can create tables in the Tables area of your App. Data can be submitted into these tables using web forms or imported from external files, such as Excel. Tables can also be exported in various file formats and saved onto your computer.

Views are created from one or more tables. You can use a view to filter the data of a table and/or include a subset of its base table. For example, if you have a table of all your global customers, you can create a view from that table to only display customers from a specific country. You can also create a view that consolidates data from multiple tables. For example, you can pull out customer records from one table and their orders from another table and show the data in a single view.

You can refer to this link to learn more about tables and views: https://howto.caspio.com/tables-and-views/

Hope that helps.