General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Network:
Windows 2003 Server
There can be something wrong with SELECT * in some situations Naomi. If a new field is added to the table, it could slow down unecessary the query as more data is transfered and this extra data may not be needed in some places. On the worst scenario, it could crash the application if the new field is not added at the end (like if you binded a grid on the result of the SELECT *).
If you do your query against a store procedure, then it may be OK to do a SELECT * from VFP. But the store procedure should not use SELECT *.
>>I heard from someone or somewhere that you should not use select table.* and, instead should list all the fields.
>>
>>I'm about to it with select table1.*, table2.field1, table2.field2... where I do need all the fields from table1, about 27 of them.
>>Anyone have any input on this and if you should not do you have the reason?
>
>If you really need all the fields from Table1, then go for it. There is nothing wrong with Select Table1.*
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only