Open GoogleCodeExporter opened 9 years ago
Hi Andrus, (Hope I don;t call the wrong name!)
DBLinq is a great idea and tool that really save us tones of time and effort.
Unfortunately some critical issues still happening as described above ... that
really draw it backward.
May I know what is the status of this issue? I'm having the same issue when
calling "ExecuteQuery<T>" (from generated DBML). It's extremely slow! I hope to
continue using this method as this give greater flexibility in Project
development.
Appreciate if any EXPERT can give some LIGHTS to this issue?
Because of this issue I turned to use Stored Procedure and that gives me
another issue as shown here
http://social.microsoft.com/Forums/zh/Offtopic/thread/4a7569d1-01f4-4136-a135-ca
e0f0df7e81?prof=required
I'm going no where now .... please!
Many thanks for any reply,
PS
Original comment by pst2...@gmail.com
on 26 Jun 2012 at 3:01
In addition to my comment earlier. Here the link I found to this Slow issue
http://www.primaryobjects.com/CMS/Article99.aspx and again the questions is
.... is this safe to apply? Should project owner review and merge the fixes for
new release version?
Just wondering DBlinq is just STOPPED at version 0.20.1 since 2010-4-16
(http://code.google.com/p/dblinq2007/). How good if we can move forward to next
release with all these critical issue resolved?
Any reply is highly appreciated.
Thanks
PS
Original comment by pst2...@gmail.com
on 26 Jun 2012 at 3:10
Original issue reported on code.google.com by
jonmpr...@gmail.com
on 9 Apr 2010 at 2:57