for SELECT queries, DbMetal can't just run the query (maybe with
adding "WHERE 1=2" to prevent long execution times) and see what
result types it gets?
In this case it would be better to use CommandBehavior.SchemaOnly
flag to invoke IDataReader.ExecuteReader(CommandBehavior behavior)

Andrus.

--
You received this message because you are subscribed to the Google Groups 
"DbLinq" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/dblinq?hl=en.

Reply via email to