Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,769 of 19,505    |
|    =?ISO-8859-1?Q?bj=F6rn_lundin?= to All    |
|    Re: Odbc and client library/drivers    |
|    21 Sep 12 03:10:54    |
      From: b.f.lundin@gmail.com              Den fredagen den 21:e september 2012 kl. 11:57:16 UTC+2 skrev bradbury9:       > > > > And here is a clearly a difference in opinion.       > > > > I do not see 'select *' as an error or as a problem.       >        > 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.              Hmm yes but that is something different.        The code cleary states that is _treats_ ALL columns.       That is not my case.              We READ all columns into structs but that does not       mean the code is looping over all fields, _treating_ them.              When an addtion/change of the code is done, the data       is already in the struct, and no need to change the sql.       Or really, no need to worry about some 'lazy' progammer       taking a shortcut assuming the data is already read from the database.              1 crash/bug less :-)                     But I respect your point of view.              --       Björn Lundin              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca