×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Charles,
This is the first time I have used all columns in my sql. As you
suggested, I normally explicitly define the columns.
But the program I am working on is an interface program which populates
a third part interface file(s). Currently there are fields in the
interface file that we don't know the value of. Those values will be
added later.
How I meant that it would save me time was that outputting a data
structure and not a list of columns was that in the near future when the
values are known I only have to assign a value to the output data
structure. I don't have to change the list of columns in the output sql
statement.
Rob
On 1/23/2017 3:45 PM, Charles Wilt wrote:
On Mon, Jan 23, 2017 at 1:40 PM, Robert Rogerson <rrogerson@xxxxxxxxxxx>
wrote:
Being able to insert from a data structure without hard coding a list of
columns will save a lot of time.
Only today...
It will take more time in the future.
Add a column to your table...now try to run your program.
SELECT * and it's equivalent of INSERT without columns named should not be
in production code when the FROM clause contains a physical table.
Charles
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.