Re: Boolean values and SQL Adapter
- From: "Mike Watson" <MikeWatson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 May 2021 05:13:16 -0700
I hit this problem sometime ago...
What I generally do is build a restricted type called SqlBool. Then set the
base data type as an xs:int. Set the 'Derived By' to Restriction... You will
then be able to set the Enumeration to the values of 0 or 1. From here you
can reference this new custom type.
- Mike Watson
> Hi and thanks for the workaround, however;
> I can not believe this is "by design" of the BizTalk 2004 team. What,
> really, is the best practice for inserting boolean/bit values using the SQL
> Best regards,
> "McGeeky" <anon@xxxxxxxx> wrote in message
> >I have had a similar issue when passing a date to a stored procedure.
> >BizTalk appends a Z to the end of the date which makes SQL Server choke.
> > An option to consider is to change the data type of the parameter in your
> > SQLServer.xsd file to a string or an integer and do the conversion to a
> > bit within the stored procedure itself.
> > --
> > McGeeky
> > http://mcgeeky.blogspot.com
> > "Christoffer" <christoffer@xxxxxxxxxx> wrote in message
> > news:%23PX$hR7VFHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
> >> Hi, I'm using the SQL Adapter to call a stored procedure in my SQL Server
> >> 2000. The stored procedure has a 'bit' parameter, which has been
> >> translated to a xs:boolean in the SQLService.xsd file. When I run my
> >> Orchestration/SQL Adapter I get an error message saying:
> >> Error converting data type nvarchar to bit
> >> Running the SQL Profiler, I see that all the parameters are passed as
> >> nvarchar, and that the boolean/bit parameter has been translated to
> >> 'true' instead of '1'. How can I solve this?
> >> Best regards,
> >> Chris
- Prev by Date: Re: HWS vs Non-HWS
- Next by Date: Re: two receive location for one orchestration
- Previous by thread: Re: Boolean values and SQL Adapter
- Next by thread: Design Help needed - Newbie
- Re: Database Independance
... Don't use vendor specific data type, (GUID in MS SQL). ... Use
stored procedure instead of functions whenever possible, ... Be careful with trigger.
- Re: SQL Express - Identity specification property - how to change
... FOO_ID int identity, ... Tony Rogerson, SQL Server MVP ... They
are making unfortunately frequent use of the IDENTITY column in conjunction with Primary Key.
... IDENTITY has none of the properties of a data type because it is not a data type at
all. ... (comp.databases.ms-sqlserver)
- Re: Type Mismatch Error Message
... >> Using Text as SQL data type. ... I created a database on a SQL
server manually and matched the column names ... I thought you "didn't use the database wizard?"
... >> Data type in form is No Constraints. ... (microsoft.public.frontpage.programming)
- Re: DISP_E_TYPEMISMATCH with OWC11
... you think its related to what data type OWC is expecting from the SQL ... I
have a SQL ... Dim objChartspace, objChart, c, objConn, objRS, axis, sql ...
An unhandled exception occurred during the execution of the ... (microsoft.public.office.developer.web.components)
- Re: Cant believe it - Back Again Already! - How to set variables to Type in SQL Statement?
... "Marshall Barton" wrote in message ... >>the way to set the SQL variables
to assume the data types of the field. ... >>would allow it to assume the data type
of the field to update to. ... > strSQLUpdate = strSQLUpdate _ ... (microsoft.public.access.modulesdaovba)