Received: by 10.224.181.83 with SMTP id bx19mr16789qab.1.1348221436327; Fri, 21 Sep 2012 02:57:16 -0700 (PDT)
Received: by 10.52.66.235 with SMTP id i11mr777808vdt.7.1348221436304; Fri, 21 Sep 2012 02:57:16 -0700 (PDT)
Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!l8no2458525qao.0!news-out.google.com!e10ni833245qan.0!nntp.google.com!l8no2458521qao.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.databases.ms-sqlserver
Date: Fri, 21 Sep 2012 02:57:16 -0700 (PDT)
In-Reply-To: <11c929ed-7994-4ef8-87af-5989e567bd01@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=195.57.19.36; posting-account=jIl9nQoAAAA9P37IIqQq64yAx-2NQYiu
NNTP-Posting-Host: 195.57.19.36
References: <94298aed-7cbb-41f8-a155-c4632fc9db35@googlegroups.com> <XnsA0D2DF54CB785Yazorman@127.0.0.1> <4486daa1-575b-4713-9ca5-f4c8654eb9c8@googlegroups.com> <XnsA0D3D87BB2DB5Yazorman@127.0.0.1> <3fe97e67-bae3-423e-9a1d-bdb938e48e7d@googlegroups.com> <XnsA0D3F197028B1Yazorman@127.0.0.1> <50cb24ed-7b00-4bd1-9de3-dc00553ea2bb@googlegroups.com> <XnsA0D4EF4453665Yazorman@127.0.0.1> <11c929ed-7994-4ef8-87af-5989e567bd01@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2bcb8b31-a822-4ce0-a97e-bd95aadd3588@googlegroups.com>
Subject: Re: Odbc and client library/drivers
From: bradbury9 <ray.bradbury9@gmail.com>
Injection-Date: Fri, 21 Sep 2012 09:57:16 +0000
Content-Type: text/plain; charset=ISO-8859-1
X-Received-Bytes: 2085
Xref: csiph.com comp.databases.ms-sqlserver:1314

> > > And here is a clearly a difference in opinion.
> > > I do not see 'select *' as an error or as a problem.

As a developer I have seen some code that generated an excel from database input using a XSLT (nothing weird so far).

get database data: select * from tablename where blablabla
for each row
    for i = 0 to data.columns
         excel.column[data.columname] = value --> BOOOOM
    end for
end for

It worked fine for almost four years, until someone added a column to a table without adding it to the XSLT. new column was not found in the transformation file.