Hi Atsushi Eno, you are the best politician I've met: if I analyze your text below, here what's to be read: 1. Pascal is good 2. We need him 3. It's easier if he doesn't ask for help (even if help can be provided) Conclusion: carry on, dude ;)
Anyway, thanks. Now for the serious part (we are serious people, aren't we): I was thinking recently to support other databases than SQL server on mono. I read somewhere in MSDN documentation that if no ProviderAttribute is specified on the typed DataContext, then the database type is guessed by Linq to SQL, based on something like internal analysis (a simple query to database?). This way, for example, in .NET 3.5 SP1, support for SQL server 2008 has appeared, without breaking the specifications. So what if Mono implementation could "guess" the database type, based on the connection string or something like this? The implementation would either be compliant and support more databases than Linq to SQL. I think we could add some internal mechanisms to link to correct database, depending on IDbConnection implementation type, for example. What do you think of that? Pascal. On Mon, Sep 8, 2008 at 15:00, Atsushi Eno <[EMAIL PROTECTED]> wrote: > > Hi Pascal, > > (It is my personal comment, not as a part of the Mono team.) > > > But I just can't give up. Some projects are still waiting for DbLinq, > > and we're not far from something usable (for a professional use). > > Leaving the project would also be unfair for people like Pablo and the > > mono team. > > Basically it is up to you whether you stop hacking dblinq or not. > You did a lot of good hacking and we appreciate much for you to have > opened the door to implement System.Data.Linq feature in Mono land. > Nothing is unfair. At least we didn't pay for you ;-) > > IF you stopped hacking and the Mono project needs Linq to SQL > functionality within certain timeframe, we will have to assign > ourselves to work on dblinq. (But I rather find it difficult and > will give up to delay our timeframe.) Such work would have happened > no matter whether there was dblinq or not. > > Having said that, the above are all for letting you to feel more > free about deciding which to go ;) We'd love you to continue your > dblinq hacking, especially people like Pablo. And there is not > many people who can drive a project that rocks. > > We can also ask the mono community widely to help dblinq effort. > Let me know if you want. That may increase your project management > mess though ;) > > Atsushi Eno > > > > -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
