Cast as int in CASE expression in SQL
I have a query that is pulling data from 10 tables and a sub-query. One of the selects is for a location and I am using a case expression to clean up the data on output. The field it is pulling the data from is varchar, and the data can be values such as: USA800, admin, ccc-ulw, ccc-ury, 002-Carson, 066-Nellis BX, 042-Junction City (there are more).
I want the case express to report back a specific value if it one of the locations that don't start with a number, but if it is a number, I want it to return just the number, as an int (dropping the 0's).
Here is the query as I have it now (the entire SQL may not be needed, but I figured it would help context):
select
ct.id as CaseID
,c.first_name as FirstName
,c.last_name as LastName
,c.id as CustomerID
,SUBSTRING(sdu.User_ID,CHARINDEX('-',sdu.User_ID)+1,(((LEN(sdu.User_ID))-CHARINDEX('-', REVERSE(sdu.User_ID)))-CHARINDEX('-',sdu.User_ID))) as [Username from Navigator]
,case sdu.Application_Name when 'Navigator' then sn.[RESP CODE] else '' end as [Responsibility Code from Navigator]
,case sdu.Application_Name when 'Navigator' then RIGHT(sn.[EMUL STATION], 4) else '' end as [CStat From Navigator]
,ce02.id as JobCode
,case l.id
when 'USA800' then 'USA800'
when 'admin' then 'Admin'
when 'ccc-ulw' then 'CCC-Lawrence'
when 'ccc-ury' then 'CCC-Raytown'
when 'ccc-usj' then 'CCC-St Joseph'
when 'ccc-uwf' then 'CCC-Wichita Falls'
else cast(SUBSTRING(l.id, 0, charindex('-', l.id, 0)) as int)
end as location
,l.id
,c2.first_name as SubmittedByFirstName
,c2.last_name as SubmittedByLastName
,sn.INST as Institution
,case sdupc.Application_Name when 'PartnerCare' then sdupc.User_ID else '' end as [Partnercare Username]
from Case_Table ct
left join Case_Type t on t.case_type_pk = ct.case_type_pk
left join Case_Category cc on cc.case_category_pk = ct.case_category_pk
left join (select max(cas.case_pk) as case_pk, customer_pk from Case_Table cas join Case_Type cat on cas.case_type_pk=cat.case_type_pk where cat.id = 'ASR' group by cas.customer_pk) ce01 on ce01.case_pk = ct.case_pk
left join Custom_Entity02 ce02 on ce02.custom_entity02_pk = ct.Virtual_JobCode
left join Customer c on ce01.customer_pk = c.customer_pk
left join Location l on l.location_pk = c.location_pk
right join Customer c2 on c2.customer_pk = ct.installed_by_customer_pk
left join Prod.dbo.Staging_DataFeed_Users sdu on sdu.User_Name = c.description and sdu.application_name = 'Navigator'
left join Prod.dbo.Staging_DataFeed_Users sdupc on sdupc.User_Name = c.description and sdupc.application_name = 'PartnerCare'
left join Prod.dbo.Staging_Navigator sn on sn.NAME = c.description and sn.NAME = sdu.User_Name
where t.id='ASR'
When running the query, I get a conversion failed error when converting the varchar
value to data type int
.
Either I am missing something, or there is a better way to do it and I am open to ideas.
The customer is expecting integer in this case (they want it to look like an integer without the leading zeros).
The results of this query are used in a foxtrot script for de-provisioning users from applications and those numbers represent branches in our bank system. The leading zeroes cause issues. If the result is a string, it is ignored.
sql-server sql-server-2014 cast
add a comment |
I have a query that is pulling data from 10 tables and a sub-query. One of the selects is for a location and I am using a case expression to clean up the data on output. The field it is pulling the data from is varchar, and the data can be values such as: USA800, admin, ccc-ulw, ccc-ury, 002-Carson, 066-Nellis BX, 042-Junction City (there are more).
I want the case express to report back a specific value if it one of the locations that don't start with a number, but if it is a number, I want it to return just the number, as an int (dropping the 0's).
Here is the query as I have it now (the entire SQL may not be needed, but I figured it would help context):
select
ct.id as CaseID
,c.first_name as FirstName
,c.last_name as LastName
,c.id as CustomerID
,SUBSTRING(sdu.User_ID,CHARINDEX('-',sdu.User_ID)+1,(((LEN(sdu.User_ID))-CHARINDEX('-', REVERSE(sdu.User_ID)))-CHARINDEX('-',sdu.User_ID))) as [Username from Navigator]
,case sdu.Application_Name when 'Navigator' then sn.[RESP CODE] else '' end as [Responsibility Code from Navigator]
,case sdu.Application_Name when 'Navigator' then RIGHT(sn.[EMUL STATION], 4) else '' end as [CStat From Navigator]
,ce02.id as JobCode
,case l.id
when 'USA800' then 'USA800'
when 'admin' then 'Admin'
when 'ccc-ulw' then 'CCC-Lawrence'
when 'ccc-ury' then 'CCC-Raytown'
when 'ccc-usj' then 'CCC-St Joseph'
when 'ccc-uwf' then 'CCC-Wichita Falls'
else cast(SUBSTRING(l.id, 0, charindex('-', l.id, 0)) as int)
end as location
,l.id
,c2.first_name as SubmittedByFirstName
,c2.last_name as SubmittedByLastName
,sn.INST as Institution
,case sdupc.Application_Name when 'PartnerCare' then sdupc.User_ID else '' end as [Partnercare Username]
from Case_Table ct
left join Case_Type t on t.case_type_pk = ct.case_type_pk
left join Case_Category cc on cc.case_category_pk = ct.case_category_pk
left join (select max(cas.case_pk) as case_pk, customer_pk from Case_Table cas join Case_Type cat on cas.case_type_pk=cat.case_type_pk where cat.id = 'ASR' group by cas.customer_pk) ce01 on ce01.case_pk = ct.case_pk
left join Custom_Entity02 ce02 on ce02.custom_entity02_pk = ct.Virtual_JobCode
left join Customer c on ce01.customer_pk = c.customer_pk
left join Location l on l.location_pk = c.location_pk
right join Customer c2 on c2.customer_pk = ct.installed_by_customer_pk
left join Prod.dbo.Staging_DataFeed_Users sdu on sdu.User_Name = c.description and sdu.application_name = 'Navigator'
left join Prod.dbo.Staging_DataFeed_Users sdupc on sdupc.User_Name = c.description and sdupc.application_name = 'PartnerCare'
left join Prod.dbo.Staging_Navigator sn on sn.NAME = c.description and sn.NAME = sdu.User_Name
where t.id='ASR'
When running the query, I get a conversion failed error when converting the varchar
value to data type int
.
Either I am missing something, or there is a better way to do it and I am open to ideas.
The customer is expecting integer in this case (they want it to look like an integer without the leading zeros).
The results of this query are used in a foxtrot script for de-provisioning users from applications and those numbers represent branches in our bank system. The leading zeroes cause issues. If the result is a string, it is ignored.
sql-server sql-server-2014 cast
add a comment |
I have a query that is pulling data from 10 tables and a sub-query. One of the selects is for a location and I am using a case expression to clean up the data on output. The field it is pulling the data from is varchar, and the data can be values such as: USA800, admin, ccc-ulw, ccc-ury, 002-Carson, 066-Nellis BX, 042-Junction City (there are more).
I want the case express to report back a specific value if it one of the locations that don't start with a number, but if it is a number, I want it to return just the number, as an int (dropping the 0's).
Here is the query as I have it now (the entire SQL may not be needed, but I figured it would help context):
select
ct.id as CaseID
,c.first_name as FirstName
,c.last_name as LastName
,c.id as CustomerID
,SUBSTRING(sdu.User_ID,CHARINDEX('-',sdu.User_ID)+1,(((LEN(sdu.User_ID))-CHARINDEX('-', REVERSE(sdu.User_ID)))-CHARINDEX('-',sdu.User_ID))) as [Username from Navigator]
,case sdu.Application_Name when 'Navigator' then sn.[RESP CODE] else '' end as [Responsibility Code from Navigator]
,case sdu.Application_Name when 'Navigator' then RIGHT(sn.[EMUL STATION], 4) else '' end as [CStat From Navigator]
,ce02.id as JobCode
,case l.id
when 'USA800' then 'USA800'
when 'admin' then 'Admin'
when 'ccc-ulw' then 'CCC-Lawrence'
when 'ccc-ury' then 'CCC-Raytown'
when 'ccc-usj' then 'CCC-St Joseph'
when 'ccc-uwf' then 'CCC-Wichita Falls'
else cast(SUBSTRING(l.id, 0, charindex('-', l.id, 0)) as int)
end as location
,l.id
,c2.first_name as SubmittedByFirstName
,c2.last_name as SubmittedByLastName
,sn.INST as Institution
,case sdupc.Application_Name when 'PartnerCare' then sdupc.User_ID else '' end as [Partnercare Username]
from Case_Table ct
left join Case_Type t on t.case_type_pk = ct.case_type_pk
left join Case_Category cc on cc.case_category_pk = ct.case_category_pk
left join (select max(cas.case_pk) as case_pk, customer_pk from Case_Table cas join Case_Type cat on cas.case_type_pk=cat.case_type_pk where cat.id = 'ASR' group by cas.customer_pk) ce01 on ce01.case_pk = ct.case_pk
left join Custom_Entity02 ce02 on ce02.custom_entity02_pk = ct.Virtual_JobCode
left join Customer c on ce01.customer_pk = c.customer_pk
left join Location l on l.location_pk = c.location_pk
right join Customer c2 on c2.customer_pk = ct.installed_by_customer_pk
left join Prod.dbo.Staging_DataFeed_Users sdu on sdu.User_Name = c.description and sdu.application_name = 'Navigator'
left join Prod.dbo.Staging_DataFeed_Users sdupc on sdupc.User_Name = c.description and sdupc.application_name = 'PartnerCare'
left join Prod.dbo.Staging_Navigator sn on sn.NAME = c.description and sn.NAME = sdu.User_Name
where t.id='ASR'
When running the query, I get a conversion failed error when converting the varchar
value to data type int
.
Either I am missing something, or there is a better way to do it and I am open to ideas.
The customer is expecting integer in this case (they want it to look like an integer without the leading zeros).
The results of this query are used in a foxtrot script for de-provisioning users from applications and those numbers represent branches in our bank system. The leading zeroes cause issues. If the result is a string, it is ignored.
sql-server sql-server-2014 cast
I have a query that is pulling data from 10 tables and a sub-query. One of the selects is for a location and I am using a case expression to clean up the data on output. The field it is pulling the data from is varchar, and the data can be values such as: USA800, admin, ccc-ulw, ccc-ury, 002-Carson, 066-Nellis BX, 042-Junction City (there are more).
I want the case express to report back a specific value if it one of the locations that don't start with a number, but if it is a number, I want it to return just the number, as an int (dropping the 0's).
Here is the query as I have it now (the entire SQL may not be needed, but I figured it would help context):
select
ct.id as CaseID
,c.first_name as FirstName
,c.last_name as LastName
,c.id as CustomerID
,SUBSTRING(sdu.User_ID,CHARINDEX('-',sdu.User_ID)+1,(((LEN(sdu.User_ID))-CHARINDEX('-', REVERSE(sdu.User_ID)))-CHARINDEX('-',sdu.User_ID))) as [Username from Navigator]
,case sdu.Application_Name when 'Navigator' then sn.[RESP CODE] else '' end as [Responsibility Code from Navigator]
,case sdu.Application_Name when 'Navigator' then RIGHT(sn.[EMUL STATION], 4) else '' end as [CStat From Navigator]
,ce02.id as JobCode
,case l.id
when 'USA800' then 'USA800'
when 'admin' then 'Admin'
when 'ccc-ulw' then 'CCC-Lawrence'
when 'ccc-ury' then 'CCC-Raytown'
when 'ccc-usj' then 'CCC-St Joseph'
when 'ccc-uwf' then 'CCC-Wichita Falls'
else cast(SUBSTRING(l.id, 0, charindex('-', l.id, 0)) as int)
end as location
,l.id
,c2.first_name as SubmittedByFirstName
,c2.last_name as SubmittedByLastName
,sn.INST as Institution
,case sdupc.Application_Name when 'PartnerCare' then sdupc.User_ID else '' end as [Partnercare Username]
from Case_Table ct
left join Case_Type t on t.case_type_pk = ct.case_type_pk
left join Case_Category cc on cc.case_category_pk = ct.case_category_pk
left join (select max(cas.case_pk) as case_pk, customer_pk from Case_Table cas join Case_Type cat on cas.case_type_pk=cat.case_type_pk where cat.id = 'ASR' group by cas.customer_pk) ce01 on ce01.case_pk = ct.case_pk
left join Custom_Entity02 ce02 on ce02.custom_entity02_pk = ct.Virtual_JobCode
left join Customer c on ce01.customer_pk = c.customer_pk
left join Location l on l.location_pk = c.location_pk
right join Customer c2 on c2.customer_pk = ct.installed_by_customer_pk
left join Prod.dbo.Staging_DataFeed_Users sdu on sdu.User_Name = c.description and sdu.application_name = 'Navigator'
left join Prod.dbo.Staging_DataFeed_Users sdupc on sdupc.User_Name = c.description and sdupc.application_name = 'PartnerCare'
left join Prod.dbo.Staging_Navigator sn on sn.NAME = c.description and sn.NAME = sdu.User_Name
where t.id='ASR'
When running the query, I get a conversion failed error when converting the varchar
value to data type int
.
Either I am missing something, or there is a better way to do it and I am open to ideas.
The customer is expecting integer in this case (they want it to look like an integer without the leading zeros).
The results of this query are used in a foxtrot script for de-provisioning users from applications and those numbers represent branches in our bank system. The leading zeroes cause issues. If the result is a string, it is ignored.
sql-server sql-server-2014 cast
sql-server sql-server-2014 cast
edited 8 hours ago
Paul White♦
50.9k14278448
50.9k14278448
asked 9 hours ago
RhondaRhonda
235
235
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Why are you casting the substring as an int in the first place? The consumer is going to expect that column to output as a string in every other case. So my suggestion: Just remove the cast.
If you only want a value to appear in the resultset when it is a valid int
, and you're on < 2012 where TRY_CAST()
is not possible, then you can say:
else case when isnumeric(SUBSTRING(l.id, 0, charindex('-', l.id, 0))) = 1
THEN CAST SUBSTRING(l.id, 0, charindex('-', l.id, 0)) AS int END
Note: ISNUMERIC()
is not a perfect validation that it is specifically an integer, but is probably fine here, since you don't really need an int
, just a string that is formatted like an int
.
Update What you can do now that I understand the requirements better is convert to an int and then back to a string. Since you are on 2014 you can use TRY_CONVERT()
:
ELSE CONVERT(varchar(12),
TRY_CONVERT(int, SUBSTRING(l.id, 0, charindex('-', l.id, 0))))
END
You might also consider fixing the design so that you don't have to parse these important bits of information out of bigger pieces of information, or at least move your CASE
expression to a computed column or a view so you don't have to put all that logic in all (or any!) of your queries.
add a comment |
If you're on SQL Server 2012 or newer, you can substitute your CAST()
function for the TRY_CAST()
function.
The difference between CAST()
and TRY_CAST()
is that the former will fail when a value cannot be converted, whereas the latter will just return a NULL value. The NULL value may not be what you want, so you should test this change carefully so you don't break anything.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229262%2fcast-as-int-in-case-expression-in-sql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Why are you casting the substring as an int in the first place? The consumer is going to expect that column to output as a string in every other case. So my suggestion: Just remove the cast.
If you only want a value to appear in the resultset when it is a valid int
, and you're on < 2012 where TRY_CAST()
is not possible, then you can say:
else case when isnumeric(SUBSTRING(l.id, 0, charindex('-', l.id, 0))) = 1
THEN CAST SUBSTRING(l.id, 0, charindex('-', l.id, 0)) AS int END
Note: ISNUMERIC()
is not a perfect validation that it is specifically an integer, but is probably fine here, since you don't really need an int
, just a string that is formatted like an int
.
Update What you can do now that I understand the requirements better is convert to an int and then back to a string. Since you are on 2014 you can use TRY_CONVERT()
:
ELSE CONVERT(varchar(12),
TRY_CONVERT(int, SUBSTRING(l.id, 0, charindex('-', l.id, 0))))
END
You might also consider fixing the design so that you don't have to parse these important bits of information out of bigger pieces of information, or at least move your CASE
expression to a computed column or a view so you don't have to put all that logic in all (or any!) of your queries.
add a comment |
Why are you casting the substring as an int in the first place? The consumer is going to expect that column to output as a string in every other case. So my suggestion: Just remove the cast.
If you only want a value to appear in the resultset when it is a valid int
, and you're on < 2012 where TRY_CAST()
is not possible, then you can say:
else case when isnumeric(SUBSTRING(l.id, 0, charindex('-', l.id, 0))) = 1
THEN CAST SUBSTRING(l.id, 0, charindex('-', l.id, 0)) AS int END
Note: ISNUMERIC()
is not a perfect validation that it is specifically an integer, but is probably fine here, since you don't really need an int
, just a string that is formatted like an int
.
Update What you can do now that I understand the requirements better is convert to an int and then back to a string. Since you are on 2014 you can use TRY_CONVERT()
:
ELSE CONVERT(varchar(12),
TRY_CONVERT(int, SUBSTRING(l.id, 0, charindex('-', l.id, 0))))
END
You might also consider fixing the design so that you don't have to parse these important bits of information out of bigger pieces of information, or at least move your CASE
expression to a computed column or a view so you don't have to put all that logic in all (or any!) of your queries.
add a comment |
Why are you casting the substring as an int in the first place? The consumer is going to expect that column to output as a string in every other case. So my suggestion: Just remove the cast.
If you only want a value to appear in the resultset when it is a valid int
, and you're on < 2012 where TRY_CAST()
is not possible, then you can say:
else case when isnumeric(SUBSTRING(l.id, 0, charindex('-', l.id, 0))) = 1
THEN CAST SUBSTRING(l.id, 0, charindex('-', l.id, 0)) AS int END
Note: ISNUMERIC()
is not a perfect validation that it is specifically an integer, but is probably fine here, since you don't really need an int
, just a string that is formatted like an int
.
Update What you can do now that I understand the requirements better is convert to an int and then back to a string. Since you are on 2014 you can use TRY_CONVERT()
:
ELSE CONVERT(varchar(12),
TRY_CONVERT(int, SUBSTRING(l.id, 0, charindex('-', l.id, 0))))
END
You might also consider fixing the design so that you don't have to parse these important bits of information out of bigger pieces of information, or at least move your CASE
expression to a computed column or a view so you don't have to put all that logic in all (or any!) of your queries.
Why are you casting the substring as an int in the first place? The consumer is going to expect that column to output as a string in every other case. So my suggestion: Just remove the cast.
If you only want a value to appear in the resultset when it is a valid int
, and you're on < 2012 where TRY_CAST()
is not possible, then you can say:
else case when isnumeric(SUBSTRING(l.id, 0, charindex('-', l.id, 0))) = 1
THEN CAST SUBSTRING(l.id, 0, charindex('-', l.id, 0)) AS int END
Note: ISNUMERIC()
is not a perfect validation that it is specifically an integer, but is probably fine here, since you don't really need an int
, just a string that is formatted like an int
.
Update What you can do now that I understand the requirements better is convert to an int and then back to a string. Since you are on 2014 you can use TRY_CONVERT()
:
ELSE CONVERT(varchar(12),
TRY_CONVERT(int, SUBSTRING(l.id, 0, charindex('-', l.id, 0))))
END
You might also consider fixing the design so that you don't have to parse these important bits of information out of bigger pieces of information, or at least move your CASE
expression to a computed column or a view so you don't have to put all that logic in all (or any!) of your queries.
edited 8 hours ago
answered 9 hours ago
Aaron Bertrand♦Aaron Bertrand
151k18287487
151k18287487
add a comment |
add a comment |
If you're on SQL Server 2012 or newer, you can substitute your CAST()
function for the TRY_CAST()
function.
The difference between CAST()
and TRY_CAST()
is that the former will fail when a value cannot be converted, whereas the latter will just return a NULL value. The NULL value may not be what you want, so you should test this change carefully so you don't break anything.
add a comment |
If you're on SQL Server 2012 or newer, you can substitute your CAST()
function for the TRY_CAST()
function.
The difference between CAST()
and TRY_CAST()
is that the former will fail when a value cannot be converted, whereas the latter will just return a NULL value. The NULL value may not be what you want, so you should test this change carefully so you don't break anything.
add a comment |
If you're on SQL Server 2012 or newer, you can substitute your CAST()
function for the TRY_CAST()
function.
The difference between CAST()
and TRY_CAST()
is that the former will fail when a value cannot be converted, whereas the latter will just return a NULL value. The NULL value may not be what you want, so you should test this change carefully so you don't break anything.
If you're on SQL Server 2012 or newer, you can substitute your CAST()
function for the TRY_CAST()
function.
The difference between CAST()
and TRY_CAST()
is that the former will fail when a value cannot be converted, whereas the latter will just return a NULL value. The NULL value may not be what you want, so you should test this change carefully so you don't break anything.
answered 9 hours ago
Daniel HutmacherDaniel Hutmacher
7,58511447
7,58511447
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229262%2fcast-as-int-in-case-expression-in-sql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown