On Sat, Jun 25, 2016 at 5:23 PM, ssatguru wrote:
> camel salesforce component has issues with dates less than or equal to
> "November 18th 1883".
>
I am intrigued to hear what is the use-case is for using dates going
so far back?
And if there is such a problem, has it been reported to jodatime
For us the usecase had to do with the default minimal datetime used by WCF
when you don't set a non nullable datetime in C#.
C# fills this datetime with 1-1-0001 and some time-part.
So really not salesforce related of course.
My solution was to provide my own formatter
What the use-case might be
I've got an update.
In 2.17.x we use jackson 1.9.12
In 2.18 we use a jackson 2.xx version
2.17.x:
* Normal jodatimes (as in not too old) don't fail;
* Old jodatimes (as in 1-1-1800) fail.
2.18:
* Normal jodatimes fail;
* Old jodatimes fail.
I propose to implement my proposed solution for 2.18 an
This seems to be a Microsoft sql server database problem.
Have you tried to run this query directly against your database.
If you get the same error, you should solve this first.
I know that Microsoft sql server support the ansi join syntax:
eg:
FROM VGMSITE s JOIN VGMLOCATION l
ON s.SITENO = l.SIT
Hello,
The parametersCount works great.
--
Kind regards,
Ronny Aerts - Intris nv - Wapenstilstandlaan 47, 2600 Berchem, Belgium
R&D Integration Architect
Prince II certified - ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: John Taylor [mailto:jtt77...@gmail.com]
Sent: zater
