StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10893677
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-06-05T08:04:04.713
FavoriteCount
0
LastActivityDate
2012-06-05T08:04:04.713
LastEditDate
LastEditorUserId
0
OwnerUserId
105929
ParentId
10888517
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Most likely you are expecting boolean short circuit to rescue the order of evaluating your WHERE clause. This is a known fallacy: boolean operator short circuit is not guaranteed in SQL. See <a href="http://rusanu.com/2009/09/13/on-sql-server-boolean-operator-short-circuit/" rel="nofollow">On SQL Server boolean operator short-circuit</a> for a discussion and proof that boolean short circuit can be skipped by query optimizer. Similar topic is <a href="http://rusanu.com/2011/08/10/t-sql-functions-do-no-imply-a-certain-order-of-execution/" rel="nofollow">T-SQL functions do no imply a certain order of execution</a>. The gist of it is that SQL is a declarative language, not an imperative one. In your case probably your cast and converts will be called for properties with IDs different from <code>property_id = 9165</code> and <code>property_active=1</code> and may attempt to cast string values that are not numerics to a numeric, hence the exception you see. Is difficult to give a precise diagnosis since so much information is missing from your problem description (like the exact definition of all object involved, including all tables, indexes, column types etc). Your best avenue is to upgrade to SQL Server 2008 and use the built in <a href="http://msdn.microsoft.com/en-us/library/cc280766.aspx" rel="nofollow">geography</a> type which has built-in support for <a href="http://msdn.microsoft.com/en-us/library/bb933808" rel="nofollow"><code>STDistance</code></a>: <blockquote> This is a close approximate to the geodesic distance. The deviation of STDistance() on common earth models from the exact geodesic distance is no more than .25%. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POError converting data type varchar to numeric CAST not working
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRemus Rusanu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COIf I could upgrade to 2008 I would. However that's several thousand dollars for a new server and licenses. My best guess is that property_lat and property_lon are my issue but converting or casting them to decimal are not working right.
 singulars
 PostPostId
 PO
 UserUserId
 USPrescient

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.