Hi Otis

I used to profiler to see how LLBLGen handles the date formats for SQL.

 @DateOfBirth = 'Sep 10 2004 12:24:50:110PM'

Now my question. Is this a hardcoded dateformat in the Libs of LLBLGen or does it change depending on the regional and sql settings?

I do nothing with date values, I just pass a System.DateTime to the parameter. The Sql profiler shows you the lowlevel execution of the query, which is not necessarily how LLBLGen Pro executes the query, but how ADO.NET executes the query.

The date value's format is coming from SqlClient, not from me.

Thanks.

wayne wrote:

Hi Otis

I used to profiler to see how LLBLGen handles the date formats for SQL.

 @DateOfBirth = 'Sep 10 2004 12:24:50:110PM'

Now my question. Is this a hardcoded dateformat in the Libs of LLBLGen or does it change depending on the regional and sql settings?

Note that the regional setting DOES effect date handling. We had a situation where our web and app servers were inadvertently built using the default US English regional settings (MM/DD/YYYY) but our Database server had Australian English (and so DD/MM/YYYY). Our queries failed because the application server was formatting date strings in US format and passing that to the DB which was attempting to interpret it in Australian format.

The fact that the SQLServer provider is passing dates as strings seems a little strange and dangerous to me but I haven't had time to look into this yet. I would have thought that dates would be passed as a DateTime datatype.

This is exactly the propblem i had. My Web Server had a different dateformat (DD/MM/YYYY) from my Database server (MM/DD/YYYY) and was receiving the date and month in the wrong order! Luckily i discovered it on the 09/09/2004 - That day saved my butt.

The date format you see in the profiler is NOT the exact value send to the server. That value is the result of the datetime tick count conversion to a string.

All DateTime values are passed as DateTime to the database, no conversion whatsoever is performed so date format issues shouldn't take place.

Otis wrote:

The date format you see in the profiler is NOT the exact value send to the server. That value is the result of the datetime tick count conversion to a string.

All DateTime values are passed as DateTime to the database, no conversion whatsoever is performed so date format issues shouldn't take place.

hmmm.... Confusing - Why did my months and days get swapped around then? - That is the reason why i looked at the sql being passed in the first place?

aha But how did you create your datetime object? perhaps you read the date/time in the wrong order? (from the form data)

I got a similar problem where sqlserver raise the following error: "Msg 8114, Level 16, State 5, Line 0

Erreur de conversion du type de données varchar en datetime. "

If ADO.NET did not send the datetime as a string, there would not be an error regarding convertion from varchar to datetime - I think- !

Is there a way to fix the datetime format ado.net send to sqlserver? Is there any other cause to that problem?

Thanks,

Hugues

please do not open an existing thread and please provide more information. See: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=7722