[Mono-list] Multiple issues with sqlmetal and MySql

[Abe Gillespie]

Yes, as far as I can tell, supplying a connection string always
results in a bug that causes DbLinq to load MS Sql Server (even when
the provider string is supplied).  This happens to me with PostgreSQL.
 I work around the problem by suppling a connection object to the
constructor instead.

On Thu, Nov 4, 2010 at 4:42 PM, Jonathan Pryor <jonpryor at vt.edu> wrote:
> On Thu, 2010-11-04 at 11:12 -0700, st0p wrote:
>> 2) When I create an instance of the generated DataContext, using a MySql
>> connection object, I´m getting the following generated sql:
>> SELECT [t0].[Email], [t0].[Id] AS [ID], [t0].[Password]
>> FROM [rss].[user] AS [t0]
>> -- Context: SqlProvider(Sql2008) Model: AttributedMetaModel Build:
>> 3.5.30729.4926
>> As you can see, the provider seems to be MSSql instead of MySql
>
> http://code.google.com/p/dblinq2007/wiki/Installation#To_use_DbLinq
>
> You need to follow solution (1) or (2), depending on what MySql allows
> you to get away with.
>
>> When I try to instantiate the context class using a connection string, it
>> also tries to connect to a MsSql server and thus times out.
>
> That sounds odd.  What connection string are you using?
>
>  - Jon
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>