Hello all:
I have some simple questions, (don't know if the answers are simple) about the pros and cons of using Views created in the MYSQL (Navicat) side of things or using the SQL Query Builder in AA to create the select statements upon which my various grids are based. There are some comments scattered in different posts across this message board which make me suspect that using views is the way to go (and perhaps this is not an a matter of choosing one or the other but knowing when to use each effectively) I would like current opinions from those with more experience than me. Thank you.
1) Performance: Which of the following is true?
Views result in faster performance.
Select Statements made in Query Builder result in faster performance.
There is no difference in performance between the two choices.
It depends (if so how and why?)
2) Features:
Are there any important features, functions or abilities that using Views gives you over using AA Query Builder Select Statements (AA QBSS) in applications
Ditto for AA QBSS over views?
Does using one or the other limit or enhance how web applications, mobile apps or desktop apps work?
Is there "killer" aspect of either that puts all other considerations aside and makes you choose one over the other?
Are there situations where you would mix it up using views in some grids and AA QBSS in others in the same application?
3) Ease of Use to create the select statements:
Here are my observations:
Navicat has the "beautify SQL" button, AA QB does not seem to have this feature.
Navicat has "View Builder" a visual of the tables, selected col's and connections, but it quickly gets like a plate of spaghetti & meatballs,
its hard to follow the lines and you can't click on the lines and edit the connections.
Navicat displays keywords in different colors
Navicat gives you hints about where errors in syntax are
AAQB automatically creates aliases for duplicate columns, Navicat does not
4) Any other points to be considered
Thank you.
I have some simple questions, (don't know if the answers are simple) about the pros and cons of using Views created in the MYSQL (Navicat) side of things or using the SQL Query Builder in AA to create the select statements upon which my various grids are based. There are some comments scattered in different posts across this message board which make me suspect that using views is the way to go (and perhaps this is not an a matter of choosing one or the other but knowing when to use each effectively) I would like current opinions from those with more experience than me. Thank you.
1) Performance: Which of the following is true?
Views result in faster performance.
Select Statements made in Query Builder result in faster performance.
There is no difference in performance between the two choices.
It depends (if so how and why?)
2) Features:
Are there any important features, functions or abilities that using Views gives you over using AA Query Builder Select Statements (AA QBSS) in applications
Ditto for AA QBSS over views?
Does using one or the other limit or enhance how web applications, mobile apps or desktop apps work?
Is there "killer" aspect of either that puts all other considerations aside and makes you choose one over the other?
Are there situations where you would mix it up using views in some grids and AA QBSS in others in the same application?
3) Ease of Use to create the select statements:
Here are my observations:
Navicat has the "beautify SQL" button, AA QB does not seem to have this feature.
Navicat has "View Builder" a visual of the tables, selected col's and connections, but it quickly gets like a plate of spaghetti & meatballs,
its hard to follow the lines and you can't click on the lines and edit the connections.
Navicat displays keywords in different colors
Navicat gives you hints about where errors in syntax are
AAQB automatically creates aliases for duplicate columns, Navicat does not
4) Any other points to be considered
Thank you.
Comment