purpose of this board, members, and what I am working on

[gmo...@gmail.com]

Hi all,
Until now, we were all sending emails to each other, but the project
has grown and we need to move to a bigger setting.

This newsgroup should allow more sharing of knowledge - we will all
see what items are being worked on, and what bugs are being reported.
Bug reports are currently coming in from some 10 people.(About hald of
the bug emails also contain a fix suggestion, fixes are mostly checked
in by me.)

People on this project active in the last month:
Douglas Six from Lille, France ported the project to SqlLite
Peter Magnusson <crippledcanary> made the SqlLite project workable
by creating the northwind script and test csproj. (Peter, which part
of the world are you from?)
Andrus - our busiest PostgreSql user - from Tallin, Estonia - did
some low-level debugging to get at some tough bugs, and provided
fixes.
Laurent Morrisau - (from France?) - MySql user, contributed bugs and
fixes
Martin Rauscher - (Germany?) provided fixes for LiveObjects
Lukas AJ Cavigelli (Switzerland) - fixes for MySql type mappings

So - thanks to Douglas and Peter for SqlLite!

Next, thanks to Andrus for providing a couple of (failing) test cases.
They boil down to hardcoded order of properties (used during a select)
changing order after a Visual Studio exception, and the select fails.
I am checking the test cases into svn today.
My employer is laying off 33,000 employees next month - so my
prioprity is to hit John Hull to prepare for upcoming job interviews.
But I still hope to fix Andrus' bugs later this week.

Next, I am working on fixes for Laurent Morisseau.
He is using JOIN clauses, and my code has pathetic errors in trivial
Joins. Fix: hopefully this weekend.

Lastly, a hard question about meaning of this project. Andrus pointed
out announcements of MySql, PostgreSql, etc support of ADO.NET entity
framework, eg on this link:
http://blogs.msdn.com/adonet/archive/2007/12/17/the-ado-net-entity-framework-not-just-for-sql-server.aspx
What are the benefits of DbLinq provider, compared to ADO.NET EF?

-jiri

[gmo...@gmail.com]

Just spotted on another thread that Peter is from Sweden ...

> framework, eg on this link:http://blogs.msdn.com/adonet/archive/2007/12/17/the-ado-net-entity-fr...

[Andrus Moor]

> What are the benefits of DbLinq provider, compared to ADO.NET EF?

I hope to use DbLinq with MONO to create application which runs in Windows,
Linux and Mac.

Linq has a much less code to implement. MONO C# 3 compiler is almost
complete.
MONO SVN includes 3.5 System.Core assembly. MONO Olive includes Linq
assemblies, all in pre-alpha through.

Entity Framework seems to have a lot of code. Porting this to Linux/Mac is
not attempted and may be never tried.

Andrus.

[crippledcanary]

I would agree to this. In the light of Entity Framework the use of
LINQ will be minimal on windows from a productivity point of view. But
I think this project has some merits from a technical point of view as
well as perhaps helping mono out abit.

I also think there would be some justification to have LINQ working on
other databases than SqlServer (I know they are talking about Linq to
Entity Framewor). It would be a shame to see this project go away.