Holy crap, the boss's back! :) 4. Most (all?) SQL engines parse strings with index starting at 1, and .NET CLR starts at 0. At the moment, we have a hack directly at SQL generation level, and it can't be optimized there. The idea was to perform the transformation where the SpecialExpression is generated, according to a flag given in IVendor. (the thread is http://groups.google.com/group/dblinq/browse_frm/thread/b9d1cc3d4a278470?tvc=1&q=string)<http://groups.google.com/group/dblinq/browse_frm/thread/b9d1cc3d4a278470?tvc=1&q=string>
5. I made a cleanup for namespaces in generated .cs file, and some "using"s are missing when we generate entities implementing INotifyPropertyChanging or INotifyPropertyChanged. Instead of adding those usings directly in .cs, it's better to add a requirement in IImplementation interface. It would list required namespaces and be used only if matching interface is requested (hope I'm clear, sure I'm not). I'm going to work on point 5 tonight. On Tue, Oct 7, 2008 at 20:51, Jiri Moudry <[EMAIL PROTECTED]> wrote: > > Here's Jiri. I will take (2). > Can you post a link to more information on 4 and 5? > > Cheers, > Jiri > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
