Groups > comp.databases.ms-sqlserver > #1539

Re: "Parameterized" Views - really that ugly?

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!.POSTED!not-for-mail
From	Ulrich Achilles <uli.achilles@googlemail.com>
Newsgroups	comp.databases.ms-sqlserver
Subject	Re: "Parameterized" Views - really that ugly?
Date	Tue, 30 Jul 2013 09:31:25 +0200
Organization	news.netcologne.de
Lines	36
Distribution	world
Message-ID	<kt7q4d$lco$1@newsreader4.netcologne.de> (permalink)
References	<kt2obm$t1d$1@newsreader4.netcologne.de> <kt3r0m$p69$1@dont-email.me>
NNTP-Posting-Host	xdsl-87-78-187-107.netcologne.de
Mime-Version	1.0
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	newsreader4.netcologne.de 1375169486 21912 87.78.187.107 (30 Jul 2013 07:31:26 GMT)
X-Complaints-To	abuse@netcologne.de
NNTP-Posting-Date	Tue, 30 Jul 2013 07:31:26 +0000 (UTC)
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
In-Reply-To	<kt3r0m$p69$1@dont-email.me>
Xref	csiph.com comp.databases.ms-sqlserver:1539

Show key headers only | View raw

On 07/28/2013 09:28 PM, Bob Barrows wrote:
> Ulrich Achilles wrote:
>> (@somedate is a monday and the view selects the courses that are
>> actual for that week).
>>
>> Of course I found soon that it is not possible to pass parameters to a
>> view in SQL server.
>
> An Access parameterized view is exactly the same as a simple SQL Server
> stored procedure, except the procedure is not directly updatable. That,
> however. is not a great loss since there is no frontend to SQL Server that
> does everything that Access does for Jet databases. The front end for a SQL
> Server database needs to provide all the functions provided by Access. This
> typically means retrieving read-only data from the database (to avoid
> locking problems) and passing parameter values to a stored procedure that
> performs updates, inserts and deletions as needed.
>
>> As a solution I created a table "parameters" with
>> just one row to hold the parameter and joined it to the courses-table:
>>
>> I came across that construction in the net, but it was commented as
>> horrible, ugly and so forth.
>>
>> My question: Is it really that bad? And why?
>
> Yes, it can be. There are so many things that can cause problems.
> Client crashes can leave bad parameter values in the table.
> Multiple users can be using each other's incorrect parameter values.
> Mainly, it's bad because it's outside of the developer's control (assuming
> that users are entering values into it).
>
>
>
Hallo,

thank you very much for your helpful explanations.

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar

Thread

"Parameterized" Views - really that ugly? Ulrich Achilles <uli.achilles@googlemail.com> - 2013-07-28 11:30 +0200
  Re: "Parameterized" Views - really that ugly? "Bob Barrows" <reb01501@NOSPAMyahoo.com> - 2013-07-28 15:28 -0400
    Re: "Parameterized" Views - really that ugly? Ulrich Achilles <uli.achilles@googlemail.com> - 2013-07-30 09:31 +0200

csiph-web