Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tomasz P. <tom...@gm...> - 2013-07-16 18:37:43
|
Hi Rob I looked at TeamCity and there is a project missing called slv-async-sparql.csproj. The relative path indicates that it sits outside of the main folder structure, which would explain why it didn't end up in the repo. Regards, Tom |
|
From: Tomasz P. <tom...@gm...> - 2013-07-16 18:20:41
|
Hi Rob, Jerin I can't recall how the Data.Sql fit in the old code. If possible I would extract the relevant part of the repository using the convert plugin (similarily to what we did with the svn->hg migration). This would give you a new repo/project with all then add dotNetRDF reference from NuGet and it's almost done. Finally a new project could be created. Maybe it's a good moment for dotNetRDF.Contrib? What do you guys think. Would you like me to try such migration? Regards, Tom On Tue, Jul 16, 2013 at 7:00 PM, Rob Vesse <rv...@do...> wrote: > Hi Jerin > > The beauty of version control is the code still exists you just have to go > back in time. > > You can find it in the closed obsolete branch in Mercurial, from a clone > of our repository (https://bitbucket.org/dotnetrdf/dotnetrdf) run the > following: > > hg up –C obsolete > > There you can find the code under Libraries\data.sql > > Or if you prefer just download the 0.7.0 source which was the last release > to include the library in an not completely deprecated state ( > http://www.dotnetrdf.org/downloads/dotnetrdf_library_source_070_beta.zip) > > The main difference between the Hash and Simple stores was in how node and > graph IDs are looked up, see the GetNodeID and GetGraphID procedure > definitions. In the hash store we used a computed column to hash data to > an integer which makes looking up existing IDs a function call and then a > simple index scan. With the simple store we don't use hashes so have to do > full/partial value based lookup which can be a lot slower. The simple > store was designed for backwards compatibility with earlier SQL Server > versions that didn't support hash functions, the Simple 2000 store is the > simple store done without computed columns which didn't support what we > need in SQL Server 2000. > > It would likely need some clean up before it can be thrown up on BitBucket > to get it to compile with the latest Core, use NuGet for dependencies etc. > and you are welcome to do that if you wish, I'm afraid I don't have time to > do it myself. > > Rob > > From: Jerin Lee <not...@bi...> > Date: Saturday, July 13, 2013 11:45 PM > To: Rob Vesse <rv...@do...> > Subject: Fwd: [Bitbucket] Suggestion about Data.Sql part (direct message) > > You are receiving this email because you're an administrator of the > dotnetrdf team. > [image: taurenshaman] *Jerin Lee* sent you a message: Hello, guys. I > love dotNetRdf very much. 3rd storage solution is a little complicated for > a individual developer. So I wanna try it with sql. I know you sotpped the > Data.Sql part. But my suggestion is that you can put the code to a seperate > project at bitbucket/github, so that you give the choosing right to > developers/users. Also maybe someone will maintain and forward it. P.S. I > viewed the resource sql file in dotNetRDF.Data.Sql.dll using JustDecompile. > Do you have some doc or words to describe the difference between > AdoHashStore.sql and AdoSimpleStore.sql. Thank you for your time. Best > wishes! > Team email forwarding can be configured from the groups > administration page <https://bitbucket.org/account/user/dotnetrdf/groups/> [image: > Bitbucket] <https://bitbucket.org> > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > |
|
From: Rob V. <rv...@do...> - 2013-07-16 17:02:02
|
Hi Jerin The beauty of version control is the code still exists you just have to go back in time. You can find it in the closed obsolete branch in Mercurial, from a clone of our repository (https://bitbucket.org/dotnetrdf/dotnetrdf) run the following: hg up C obsolete There you can find the code under Libraries\data.sql Or if you prefer just download the 0.7.0 source which was the last release to include the library in an not completely deprecated state (http://www.dotnetrdf.org/downloads/dotnetrdf_library_source_070_beta.zip) The main difference between the Hash and Simple stores was in how node and graph IDs are looked up, see the GetNodeID and GetGraphID procedure definitions. In the hash store we used a computed column to hash data to an integer which makes looking up existing IDs a function call and then a simple index scan. With the simple store we don't use hashes so have to do full/partial value based lookup which can be a lot slower. The simple store was designed for backwards compatibility with earlier SQL Server versions that didn't support hash functions, the Simple 2000 store is the simple store done without computed columns which didn't support what we need in SQL Server 2000. It would likely need some clean up before it can be thrown up on BitBucket to get it to compile with the latest Core, use NuGet for dependencies etc. and you are welcome to do that if you wish, I'm afraid I don't have time to do it myself. Rob From: Jerin Lee <not...@bi...> Date: Saturday, July 13, 2013 11:45 PM To: Rob Vesse <rv...@do...> Subject: Fwd: [Bitbucket] Suggestion about Data.Sql part (direct message) > > > > You are receiving this email because you're an administrator of the > dotnetrdf team. > > > > > Jerin Lee sent you a message: > Hello, guys. I love dotNetRdf very much. 3rd storage solution is a little > complicated for a individual developer. So I wanna try it with sql. I know you > sotpped the Data.Sql part. But my suggestion is that you can put the code to a > seperate project at bitbucket/github, so that you give the choosing right to > developers/users. Also maybe someone will maintain and forward it. P.S. I > viewed the resource sql file in dotNetRDF.Data.Sql.dll using JustDecompile. Do > you have some doc or words to describe the difference between AdoHashStore.sql > and AdoSimpleStore.sql. Thank you for your time. Best wishes! > > > > Team email forwarding can be configured from the groups administration > page <https://bitbucket.org/account/user/dotnetrdf/groups/> > <https://bitbucket.org> > |
|
From: <tr...@do...> - 2013-07-12 07:52:17
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Portable Class Library should not include inappropriate synchronous APIs</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Kal</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-12 08:51 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
+1 on taking out the sync methods - they are really inappropriate for PCL. However, the reason they are there is that there isn't as good a level of coverage over the async APIs in the unit tests at the moment. You may want to factor in the work required to add more async unit tests as part of the work for this item. I'd be happy to help out with this if I can get some guidance from you on coding style / content for unit tests.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 23:14:55
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Portable Class Library should not include inappropriate synchronous APIs</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Category changed from "Unassigned" to "Build, Release and Testing"
</li>
<li>Issue Type changed from "Unassigned" to "Improvement"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 23:13:43
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlRemoteEndpoint async methods don't propagate errors correctly</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0 %" to "40 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 23:13:26
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlRemoteEndpoint async methods don't propagate errors correctly</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-12 12:12 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Have this fixed for SparqlRemoteEndpoint, need to review other similar APIs to make sure they are capable of propagating errors appropriately</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 23:09:22
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Portable Class Library should not include inappropriate synchronous APIs</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Progress changed from "0 %" to "80 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2013-07-11 22:36:28
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 4 new changesets (Bitbucket) 2. commit/dotnetrdf: rvesse: Ignore a query timeout test that intermittently fails, analysis shows that given a good machine it is suprisingly easy to complete the query under the 1ms timeout (Bitbucket) 3. commit/dotnetrdf: 5 new changesets (Bitbucket) 4. commit/dotnetrdf: 11 new changesets (Bitbucket) 5. commit/dotnetrdf: 2 new changesets (Bitbucket) 6. commit/dotnetrdf: rvesse: Note addition of first version of Fluent Query builder API in Change Log (CORE-260) (Bitbucket) 7. commit/dotnetrdf: rvesse: Close the symbol-packages branch (CORE-361) (Bitbucket) 8. commit/dotnetrdf: rvesse: Tweaks to get symbol packages built correctly (CORE-361) (Bitbucket) 9. commit/dotnetrdf: 11 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Fri, 05 Jul 2013 22:03:07 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9c4cdc63fdf4/ Changeset: 9c4cdc63fdf4 User: rvesse Date: 2013-07-05 23:53:09 Summary: Fix missing license headers Affected #: 19 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6623849c537e/ Changeset: 6623849c537e User: rvesse Date: 2013-07-05 23:59:11 Summary: Update Change Log to note CORE-367 changes Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/831a393b4aa7/ Changeset: 831a393b4aa7 User: rvesse Date: 2013-07-06 00:00:42 Summary: Correct XML docs on new Options properties to reflect actual defaults (CORE-367) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9f2e868054e8/ Changeset: 9f2e868054e8 User: rvesse Date: 2013-07-06 00:02:41 Summary: Make SPARQL ordering use new comparison options where appropriate (CORE-367) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Fri, 05 Jul 2013 22:05:19 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Ignore a query timeout test that intermittently fails, analysis shows that given a good machine it is suprisingly easy to complete the query under the 1ms timeout To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/97c6c99e92e5/ Changeset: 97c6c99e92e5 User: rvesse Date: 2013-07-06 00:05:08 Summary: Ignore a query timeout test that intermittently fails, analysis shows that given a good machine it is suprisingly easy to complete the query under the 1ms timeout Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Fri, 05 Jul 2013 22:25:46 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 5 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4e43b5200163/ Changeset: 4e43b5200163 User: rvesse Date: 2013-07-06 00:15:02 Summary: Use $version$ simple for inter-library dependencies in NuSpec files (CORE-361) Affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/27263c02ce9d/ Changeset: 27263c02ce9d User: rvesse Date: 2013-07-06 00:17:36 Summary: Include symbol package targets as dependencies of dist-libs-nuget target (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e83dd12b2479/ Changeset: e83dd12b2479 User: rvesse Date: 2013-07-06 00:22:25 Summary: Update Build and Release process note (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3b534d956511/ Changeset: 3b534d956511 User: rvesse Date: 2013-07-06 00:24:43 Summary: Update Release Notes in NuSpec files (CORE-361) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b234039f726d/ Changeset: b234039f726d User: rvesse Date: 2013-07-06 00:25:26 Summary: Update Release Notes in NuSpec files (CORE-361) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Fri, 05 Jul 2013 23:12:56 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 11 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 11 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fad55ae98bcc/ Changeset: fad55ae98bcc User: rvesse Date: 2013-07-06 00:32:57 Summary: Add upload targets for symbol packages (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/65113ecd4706/ Changeset: 65113ecd4706 Branch: symbol-packages User: rvesse Date: 2013-07-06 00:33:38 Summary: Merge latest changes from default to symbol-packages branch (CORE-361) Affected #: 396 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/082b3769855d/ Changeset: 082b3769855d Branch: symbol-packages User: rvesse Date: 2013-07-06 00:35:17 Summary: Start simplifying symbol package setup (CORE-361) Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dfef69c3cf2a/ Changeset: dfef69c3cf2a Branch: symbol-packages User: rvesse Date: 2013-07-06 00:42:17 Summary: Really simplify symbol package creation (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/03fdd3b2d2dc/ Changeset: 03fdd3b2d2dc Branch: symbol-packages User: rvesse Date: 2013-07-06 00:44:53 Summary: Really simplify symbol package creation (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5b6967a4c7dd/ Changeset: 5b6967a4c7dd Branch: symbol-packages User: rvesse Date: 2013-07-06 00:45:56 Summary: Update NuSpec release notes (CORE-361) Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/01b609e8a9e3/ Changeset: 01b609e8a9e3 Branch: symbol-packages User: rvesse Date: 2013-07-06 00:47:57 Summary: Bump revision to 2713 to prepare a pre-release to check symbol package refactoring (CORE-361) Affected #: 32 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/11e70f04c49f/ Changeset: 11e70f04c49f Branch: symbol-packages User: rvesse Date: 2013-07-06 00:48:43 Summary: Update nuspecversion in NAnt file in preparation for pre-release candidate (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e01ab56fd05f/ Changeset: e01ab56fd05f Branch: symbol-packages User: rvesse Date: 2013-07-06 00:49:31 Summary: Use a valid NuSpec version string (CORE-361) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/517ebbf88c76/ Changeset: 517ebbf88c76 Branch: symbol-packages User: rvesse Date: 2013-07-06 01:12:10 Summary: Some more tweaks to symbol package setup (CORE-361) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ed29e9c61e61/ Changeset: ed29e9c61e61 User: rvesse Date: 2013-07-06 01:12:32 Summary: Merge in latest symbol packages improvements (CORE-361) Affected #: 40 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Fri, 05 Jul 2013 23:20:33 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/980c00b865eb/ Changeset: 980c00b865eb Branch: sparql-ops User: rvesse Date: 2013-07-06 01:16:02 Summary: Merge latest changes to sparql-ops branch Affected #: 114 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9a8e637a1867/ Changeset: 9a8e637a1867 Branch: virtuoso-7 User: rvesse Date: 2013-07-06 01:19:29 Summary: Merge latest changes to virtuoso-7 branch Affected #: 560 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Fri, 05 Jul 2013 23:22:34 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Note addition of first version of Fluent Query builder API in Change Log (CORE-260) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3bcf1f4f7803/ Changeset: 3bcf1f4f7803 User: rvesse Date: 2013-07-06 01:22:24 Summary: Note addition of first version of Fluent Query builder API in Change Log (CORE-260) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Tue, 09 Jul 2013 17:34:17 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Close the symbol-packages branch (CORE-361) To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9ccee3dbd932/ Changeset: 9ccee3dbd932 Branch: symbol-packages User: rvesse Date: 2013-07-09 19:34:02 Summary: Close the symbol-packages branch (CORE-361) Affected #: 0 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Tue, 09 Jul 2013 17:32:31 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Tweaks to get symbol packages built correctly (CORE-361) To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c395eb87e029/ Changeset: c395eb87e029 User: rvesse Date: 2013-07-09 19:32:13 Summary: Tweaks to get symbol packages built correctly (CORE-361) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Thu, 11 Jul 2013 22:36:19 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 11 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 11 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1324a915ae7e/ Changeset: 1324a915ae7e User: rvesse Date: 2013-07-11 18:53:36 Summary: Remove defunct code Affected #: 9 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2e843a4bf370/ Changeset: 2e843a4bf370 User: rvesse Date: 2013-07-11 19:39:47 Summary: Improve sanity check pre-commit hook script Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b876c30e034c/ Changeset: b876c30e034c User: rvesse Date: 2013-07-11 19:41:06 Summary: Improve sanity check pre-commit hook script Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ee22ff1ed8db/ Changeset: ee22ff1ed8db User: rvesse Date: 2013-07-11 19:41:24 Summary: Improve sanity check pre-commit hook script Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4d1b63e78f05/ Changeset: 4d1b63e78f05 Branch: CORE-370 User: rvesse Date: 2013-07-11 23:20:27 Summary: Make SparqlRemoteEndpoint.QueryWithResultSet() async variant propagate errors via the state parameter of the callback (CORE-370) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/359ad40b7b2d/ Changeset: 359ad40b7b2d Branch: CORE-370 User: rvesse Date: 2013-07-11 23:41:03 Summary: Make other async SparqlRemoteEndpoint async calls propagate errors via the state parameter of the callback (CORE-370) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e2a7719457a2/ Changeset: e2a7719457a2 Branch: CORE-371 User: rvesse Date: 2013-07-11 23:48:58 Summary: Remove defunct debugging core (CORE-371, CORE-303) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8f8d5dc50833/ Changeset: 8f8d5dc50833 Branch: CORE-371 User: rvesse Date: 2013-07-12 00:06:22 Summary: Remove unsafe sync -> async API bridges (CORE-371) Affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d4da2c0658e2/ Changeset: d4da2c0658e2 Branch: CORE-371 User: rvesse Date: 2013-07-12 00:15:01 Summary: ifdef out all tests that cover unsupported APIs on the PCL platform (CORE-371, CORE-303) Affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1e032ef96689/ Changeset: 1e032ef96689 Branch: CORE-371 User: rvesse Date: 2013-07-12 00:25:26 Summary: Remove more unsafe sync -> async API bridges (CORE-371) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/db272a56f1f1/ Changeset: db272a56f1f1 Branch: CORE-370 User: rvesse Date: 2013-07-12 00:34:55 Summary: Merge CORE-371 changes into CORE-370 branch Affected #: 21 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 10, Issue 2 ************************************************ |
|
From: <tr...@do...> - 2013-07-11 22:25:51
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Portable Class Library should not include inappropriate synchronous APIs</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Planned" to "In Progress"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 21:40:08
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Portable Class Library should not include inappropriate synchronous APIs</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Currently the work from CORE-303 means that in the PCL builds some synchronous APIs are included that rely on calling their async alternatives and blocking on the response which will break if they are used under certain platforms.</p>
<p>
</p>
<p>
It would be better to have the PCL builds not use any synchronous APIs which are not safe across all platforms.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=371</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 21:26:35
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlRemoteEndpoint async methods don't propagate errors correctly</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Description changed from "<p>
A user has reported an issue using the async query methods under SIlverlight. On debugging the issue appears to be down to the async code in SparqlRemoteEndpoint not handling and propagating errors appropriately.</p>" to "<p>
A user has reported an issue using the async query methods under SIlverlight which results in an apparent app hang.</p>
<p>
</p>
<p>
On debugging the issue appears to be down to the async code in SparqlRemoteEndpoint not handling and propagating errors appropriately. So the code is not hanging rather it is producing an unhandled error which simply dissapears from the POV of the user hence the apparent hang.</p>"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 21:07:34
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add some "lazyness" to algebra evaluation</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Max</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 10:06 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Thanks for pointing the Medusa link and also the infringement of the specification, I was not fully aware the bind ended the graph pattern, and was thinking in term of scope.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 21:03:23
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlRemoteEndpoint async methods don't propagate errors correctly</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 10:02 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Not sure that the API in the current from can handle propagating exceptions correctly because the callback has no way to return errors other than by abusing the state return. This may be the shortest path to fixing this for 1.0.1 and we can introduce a better async API for this later.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:52:01
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlRemoteEndpoint async methods don't propagate errors correctly</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A user has reported an issue using the async query methods under SIlverlight. On debugging the issue appears to be down to the async code in SparqlRemoteEndpoint not handling and propagating errors appropriately.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:12:26
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for latest W3C drafts for TriG</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Milestone changed from "1.1.0" to "Unscheduled"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:12:11
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for latest W3C drafts for TriG</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 09:11 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Pushing back to unscheduled, recent RDF WG discussions indicate that the spec is subject to (violent) change and I don't want to waste the precious time I do have to work on dotNetRDF on implementing something I will only have to re-implement</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:10:32
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>RDF/XML parser should allow element names with xml: prefix</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "Completed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.0"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=358" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=358</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:10:21
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>RDF/XML parser should allow element names with xml: prefix</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 09:09 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Got fixed in 1.0.0 but never marked as such</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=358" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=358</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:07:01
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Provide a Portable Class Library build of dotNetRDF</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Planned" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Completed"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:06:52
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Provide a Portable Class Library build of dotNetRDF</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 09:05 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The work on this from Kal was recently integrated into default</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:05:15
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add some "lazyness" to algebra evaluation</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Unknown" to "Closed"
</li>
<li>Milestone changed from "Unassigned" to "Unscheduled"
</li>
<li>Resolution changed from "Unassigned" to "Invalid"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-11 20:04:51
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add some "lazyness" to algebra evaluation</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-11 09:03 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The query engine already includes lazy evaluation where possible but your query is not eligible. This is primarily because you use DISTINCT which means it needs to materialize the all the results before throwing away the duplicates though there are other aspects of your query that block lazy evaluation (the use of a non-trivial ORDER BY). Generally speaking query evaluation could be lazier but this is not easily done within the current architecture, see <a href="https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Architecture/Design/Medusa">https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Architecture/Design/Medusa</a> for some design thinking on future rearchitecting to this effect.</p>
<p>
</p>
<p>
Regardless the engine cannot make an arbitrary decision to change the query to apply the BIND where you are suggesting since that would mean disregarding the SPARQL specification.</p>
<p>
</p>
<p>
Note that you can force the engine to evaluate the query in the order you want by using a sub-query which forces things to be evaluated earlier:</p>
<p>
</p>
<div>
SELECT ?org ?hasBlogPost ?hasEvent ?hasJobOffer ?hasProduct ?hasGoodDeal ?isWebSite {</div>
<div>
FILTER (NOT EXISTS{ ?org a my:PortalSite }) .</div>
<div>
BIND ( EXISTS { ?item a my:BlogPost . ?item my:authoredBy ?org} as ?hasBlogPost) .</div>
<div>
BIND ( EXISTS { ?item a my:Event. ?item my:authoredBy ?org} as ?hasEvent) .</div>
<div>
BIND ( EXISTS { ?item a my:JobOffer. ?item my:authoredBy ?org} as ?hasJobOffer) .</div>
<div>
BIND ( EXISTS { ?item a my:ProductOrService . ?item my:authoredBy ?org} as ?hasProduct) .</div>
<div>
BIND ( EXISTS { ?item a my:GoodDeal . ?item my:authoredBy ?org} as ?hasGoodDeal) .</div>
<div>
BIND (EXISTS{?org a my:PersonalSite } as ?isWebSite)</div>
<div>
{</div>
<div>
SELECT DISTINCT ?org ?lbl</div>
<div>
WHERE</div>
<div>
{</div>
<div>
?org rdfs:label ?lbl . ?org a my:Organization</div>
<div>
} ORDER BY DESC(?isWebSite) ASC(?lbl) LIMIT 10</div>
<div>
}</div>
<div>
}</div>
<p>
</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-10 19:56:32
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add some "lazyness" to algebra evaluation</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Max</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-07-10 08:55 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
EDIT</p>
<p>
<span id="ctl00_ctl00_ctl00_MainContent_Content_IssueFields_Description">I was wondering if it would not be too difficult to make the engine evaluate these algebras later <strong>when </strong>they are really needed since they do not take any part in filtering the result set ?</span></p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-07-10 19:50:33
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add some "lazyness" to algebra evaluation</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Max</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Low</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi Rob,<br />
<br />
I just encountered this use-case on a store I'm testing.</p>
<p>
The store currently amounts to ~140K triples and comprise 3000 organisations<br />
I made this query to get pages of 10 organisations, and added bindings to check when to activate tabs depending on whether or not the organisation authored a specific item type:<br />
<br />
SELECT DISTINCT ?org ?hasBlogPost ?hasEvent ?hasJobOffer ?hasProduct ?hasGoodDeal ?isWebSite {<br />
FILTER (NOT EXISTS{ ?org a my:PortalSite }) .<br />
BIND ( EXISTS { ?item a my:BlogPost . ?item my:authoredBy ?org} as ?hasBlogPost) .<br />
BIND ( EXISTS { ?item a my:Event. ?item my:authoredBy ?org} as ?hasEvent) .<br />
BIND ( EXISTS { ?item a my:JobOffer. ?item my:authoredBy ?org} as ?hasJobOffer) .<br />
BIND ( EXISTS { ?item a my:ProductOrService . ?item my:authoredBy ?org} as ?hasProduct) .<br />
BIND ( EXISTS { ?item a my:GoodDeal . ?item my:authoredBy ?org} as ?hasGoodDeal) .<br />
BIND (EXISTS{?org a my:PersonalSite } as ?isWebSite)<br />
. ?org rdfs:label ?lbl . ?org a my:Organization<br />
} ORDER BY DESC(?isWebSite) ASC(?lbl) LIMIT 10<br />
<br />
As it is the optimizer converts the query to this algebra:<br />
<br />
Slice(Distinct(Select(OrderBy(Extend(Extend(Extend(Extend(Extend(Join(Extend(Filter(BGP(?result <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.example.com/schema#Organization>), NOT EXISTS { ?result <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.example.com/schema#PortalSite> . }))), BGP(?result <http://www.w3.org/2000/01/rdf-schema#label> ?var12)))))))))), LIMIT 10, OFFSET 0)<br />
<br />
So of course, all of the Extend algebras get evaluated for the whole dataset before ordering/slicing/distincting.<br />
<br />
I was wondering if it would not be too difficult to make the engine evaluate these algebras later as they are really needed since they do not take any part in filtering the result set ?<br />
<br />
In my case the query "plan" would become something like :<br />
<br />
Select(Extend(Extend(Extend(Extend(Extend(Slice(Distinct(OrderBy(Join(Extend(Filter(BGP(?result <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.example.com/schema#Organization>), NOT EXISTS { ?result <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.example.com/schema#PortalSite> . }))), BGP(?result <http://www.w3.org/2000/01/rdf-schema#label> ?var12)))), LIMIT 10, OFFSET 0)))))))<br />
<br />
Meaning that all the bindings (except for the isWebSite var that is required by the OrderBy clause) are avaluate once the resultset is computed, resulting in much less evaluations if I'm right.<br />
<br />
I took the Extend algebra example since it is the main pattern in my query but I believe it could (perhaps already is?) be extended to some other algebra ?<br />
<br />
I'm not sure whether or not the performance gain is worth the effort, but I think it worth the consideration anyway ;)<br />
<br />
Max.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=369</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
48 messages has been excluded from this view by a project administrator.
