| Subject | RE: [firebird-support] What pratice is better? |
|---|---|
| Author | David Johnson |
| Post date | 2005-08-26T04:23:18Z |
To which I would add this note: Make sure what you are hitting is a
nail before you decide which hammer to use. You may really need a
screwdriver.
It seems odd to me that the _application_ would determine what parts of
tables are to be viewed, rather than the user's privileges. The
database should not care what application is requesting information,
only whether the user of the application has the appropriate rights to
see that information.
Is the issue simply that you want to specify your selection criteria and
limit the number of columns returned? If so, then the question is
usually a matter of personal preference because that is exactly what SQL
(whether it resides on the server or the client) does for the
applications programmer. Without more specifics, your question is
approximately on the scale of "Which eggs are better - fried or
poached?"
Or, is the issue a security and authorization issue? If this is the
case, then I think you need to restate the problem in business terms (no
geek-speak) to get a useful response. A full specification of the
business problem's parameters might be more useful in this case than a
question that starts with a possibly inappropriate technical solution.
Either way, once the full parameters of the business problem are
expressed, then we can lapse into our native geek and produce a better
answer.
nail before you decide which hammer to use. You may really need a
screwdriver.
It seems odd to me that the _application_ would determine what parts of
tables are to be viewed, rather than the user's privileges. The
database should not care what application is requesting information,
only whether the user of the application has the appropriate rights to
see that information.
Is the issue simply that you want to specify your selection criteria and
limit the number of columns returned? If so, then the question is
usually a matter of personal preference because that is exactly what SQL
(whether it resides on the server or the client) does for the
applications programmer. Without more specifics, your question is
approximately on the scale of "Which eggs are better - fried or
poached?"
Or, is the issue a security and authorization issue? If this is the
case, then I think you need to restate the problem in business terms (no
geek-speak) to get a useful response. A full specification of the
business problem's parameters might be more useful in this case than a
question that starts with a possibly inappropriate technical solution.
Either way, once the full parameters of the business problem are
expressed, then we can lapse into our native geek and produce a better
answer.
On Fri, 2005-08-26 at 13:16 +1000, Alan McDonald wrote:
> > Hi:
> >
> > I have a database with some tables, depending on what client application
> > calls the table, I must show only a portion of some of these tables, both
> > horizontaly and verticaly. There are two different methods: Views in the
> > server side or Queries in the client side.
> >
> > I want to know what practice is better, and of course witch of them offer
> > better performance.
> >
> > Thanks in advance
> >
> > Fernando
>
> A view is just a query stored at the server and executed when you ask for
> it.
> Very little diff in performance.
> Alan
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>