Re: [Sedna-discussion] question related to external global variables
Hello Sedna Team,
Is there a new deadline to the Sedna 4.0 release? or Sedna 3.6?
Regards,
On Tue, Nov 13, 2012 at 11:48 AM, Flávio R. C. Sousa flavioso...@ufc.brwrote:
Hi Sedna Team,
Thanks for your feedback. I'm looking forward for the new release. Good
luck.
Regards,
On Tue, Nov 13, 2012 at 9:28 AM, Олег Борисенко a...@somestuff.ru wrote:
We have no deadline and no ideas when exactly we will finish everything.
We have 3 directions to finish still:
1) arch
2) new testing system
3) check that everything works after merge with Ilyas' new optimizer
branch.
Until everything will be checked there's no new release. It's hard to
forecast the time it takes because there is a lot of current interrupting
work on other things. It will be finished for sure but we don't know when
exactly
On Tue, Nov 13, 2012 at 2:00 PM, Ivan Shcheklein shchekl...@gmail.comwrote:
Oleg, Ilya can you enlighten us on this? :) I definitely don't have
enough information to answer this question.
Is there a new deadline to the Sedna 4.0 release?
On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ruwrote:
We *hope* that we will be able to release aplha version by 10.10.2012
but it's not a deadline : if something would be broken by that moment we
will not be able to make a release
On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa
flavioso...@ufc.br wrote:
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ruwrote:
Well, it's not ready yet and it's not a guarantee that everything
would work as expected. But we hope that we would be able to make the
following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements
for some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is
wrong with one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need
just to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible
to hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna
is listening to.
5. It would be possible to start sedna as windows service
natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session.
It would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes
that would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should
result in better code quality
13. clang/llvm compiler support (it's working now too but we
should check that everything is okay)
I could forget something, but these are common new features that we
are working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко
a...@somestuff.ruwrote:
We are working hard on Sedna 4.0 and it's not too simple to have a
trip anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster
char...@cfoster.net wrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers
robby.pelss...@nxp.com wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to
set properties but there's also nothing stopping me from storing XML
in
Sedna containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com]
On Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external
global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have
external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as
xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library
Re: [Sedna-discussion] question related to external global variables
We are trying to release 3.6 by 15 July -- we have started the process of production testing a month ago and as all the tests will be finished, we will make a new release (3.6). Sedna 4.0 alpha version should be ready by the 31 of August, but it is still not a promise: we are working on it. On Sun, Jun 16, 2013 at 9:48 PM, Flávio R. C. Sousa flavioso...@ufc.brwrote: Hello Sedna Team, Is there a new deadline to the Sedna 4.0 release? or Sedna 3.6? Regards, On Tue, Nov 13, 2012 at 11:48 AM, Flávio R. C. Sousa flavioso...@ufc.brwrote: Hi Sedna Team, Thanks for your feedback. I'm looking forward for the new release. Good luck. Regards, On Tue, Nov 13, 2012 at 9:28 AM, Олег Борисенко a...@somestuff.ru wrote: We have no deadline and no ideas when exactly we will finish everything. We have 3 directions to finish still: 1) arch 2) new testing system 3) check that everything works after merge with Ilyas' new optimizer branch. Until everything will be checked there's no new release. It's hard to forecast the time it takes because there is a lot of current interrupting work on other things. It will be finished for sure but we don't know when exactly On Tue, Nov 13, 2012 at 2:00 PM, Ivan Shcheklein shchekl...@gmail.comwrote: Oleg, Ilya can you enlighten us on this? :) I definitely don't have enough information to answer this question. Is there a new deadline to the Sedna 4.0 release? On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ruwrote: We *hope* that we will be able to release aplha version by 10.10.2012 but it's not a deadline : if something would be broken by that moment we will not be able to make a release On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa flavioso...@ufc.br wrote: Very cool. Do you have some deadline to released? On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ruwrote: Well, it's not ready yet and it's not a guarantee that everything would work as expected. But we hope that we would be able to make the following: 1. New numbering scheme. It should result in much smaller disk utilization. 2. Query optimizer. It should result in performance improvements for some types of queries. 3. Reduction of semaphores usage. 4. Database wouldn't depend one on another. It something is wrong with one database, it wouldn't crash others. 5. New front-end architecture: 1. Database management become client-side --- you would need just to connect se_gov to create/delete/start/stop databases 2. Asynchronious messaging protocol: it would be impossible to hang sedna from outside 3. No need for pping 4. It would be possible to specify many interfaces that sedna is listening to. 5. It would be possible to start sedna as windows service natively. 6. New protocol 7. Pool of trn's: se_trn wouldn't die after each session. It would result in much faster small transactions. 8. (maybe) diagnostic messaging channel for se_trn processes that would indicate transactions progress. 9. (maybe not in v4.0 but v4.1) rest api 10. (maybe not in v4.0 but v4.1) some sort of embedded sedna 11. (maybe) openssl library for connections encryption 12. internal unit-tests and new testing system that should result in better code quality 13. clang/llvm compiler support (it's working now too but we should check that everything is okay) I could forget something, but these are common new features that we are working on :) On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa flaviocso...@gmail.com wrote: What's new features in Sedna 4.0 ? On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ruwrote: We are working hard on Sedna 4.0 and it's not too simple to have a trip anywhere at this moment :) On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.net wrote: Will you be at XML Amsterdam on Wednesday? And will any other people who are on this list be there? On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com wrote: Hi Charles, Excellent suggestion. It's not the usual approach we take to set properties but there's also nothing stopping me from storing XML in Sedna containing properties. Brilliant workaround ;-) Thx, Robby -Original Message- From: charles.fos...@gmail.com [mailto: charles.fos...@gmail.com] On Behalf Of Charles Foster Sent: Thursday, September 13, 2012 12:52 PM To: Robby Pelssers Cc: sedna-discussion@lists.sourceforge.net Subject: Re: [Sedna-discussion] question related to external global variables Hi Robby, XQuery Library Modules (stored in Sedna) [1] can not have external variables. Only XQuery Main Modules (i.e. Ad-hoc queries) can have external variables, you can bind these from the XQJ driver. You could set a constant
Re: [Sedna-discussion] question related to external global variables
Thanks for your feedback. Great. What's new features in Sedna 3.6 ? On Sun, Jun 16, 2013 at 5:00 PM, Олег Борисенко a...@somestuff.ru wrote: We are trying to release 3.6 by 15 July -- we have started the process of production testing a month ago and as all the tests will be finished, we will make a new release (3.6). Sedna 4.0 alpha version should be ready by the 31 of August, but it is still not a promise: we are working on it. On Sun, Jun 16, 2013 at 9:48 PM, Flávio R. C. Sousa flavioso...@ufc.brwrote: Hello Sedna Team, Is there a new deadline to the Sedna 4.0 release? or Sedna 3.6? Regards, On Tue, Nov 13, 2012 at 11:48 AM, Flávio R. C. Sousa flavioso...@ufc.brwrote: Hi Sedna Team, Thanks for your feedback. I'm looking forward for the new release. Good luck. Regards, On Tue, Nov 13, 2012 at 9:28 AM, Олег Борисенко a...@somestuff.ru wrote: We have no deadline and no ideas when exactly we will finish everything. We have 3 directions to finish still: 1) arch 2) new testing system 3) check that everything works after merge with Ilyas' new optimizer branch. Until everything will be checked there's no new release. It's hard to forecast the time it takes because there is a lot of current interrupting work on other things. It will be finished for sure but we don't know when exactly On Tue, Nov 13, 2012 at 2:00 PM, Ivan Shcheklein shchekl...@gmail.comwrote: Oleg, Ilya can you enlighten us on this? :) I definitely don't have enough information to answer this question. Is there a new deadline to the Sedna 4.0 release? On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ruwrote: We *hope* that we will be able to release aplha version by 10.10.2012 but it's not a deadline : if something would be broken by that moment we will not be able to make a release On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa flavioso...@ufc.br wrote: Very cool. Do you have some deadline to released? On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ruwrote: Well, it's not ready yet and it's not a guarantee that everything would work as expected. But we hope that we would be able to make the following: 1. New numbering scheme. It should result in much smaller disk utilization. 2. Query optimizer. It should result in performance improvements for some types of queries. 3. Reduction of semaphores usage. 4. Database wouldn't depend one on another. It something is wrong with one database, it wouldn't crash others. 5. New front-end architecture: 1. Database management become client-side --- you would need just to connect se_gov to create/delete/start/stop databases 2. Asynchronious messaging protocol: it would be impossible to hang sedna from outside 3. No need for pping 4. It would be possible to specify many interfaces that sedna is listening to. 5. It would be possible to start sedna as windows service natively. 6. New protocol 7. Pool of trn's: se_trn wouldn't die after each session. It would result in much faster small transactions. 8. (maybe) diagnostic messaging channel for se_trn processes that would indicate transactions progress. 9. (maybe not in v4.0 but v4.1) rest api 10. (maybe not in v4.0 but v4.1) some sort of embedded sedna 11. (maybe) openssl library for connections encryption 12. internal unit-tests and new testing system that should result in better code quality 13. clang/llvm compiler support (it's working now too but we should check that everything is okay) I could forget something, but these are common new features that we are working on :) On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa flaviocso...@gmail.com wrote: What's new features in Sedna 4.0 ? On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ruwrote: We are working hard on Sedna 4.0 and it's not too simple to have a trip anywhere at this moment :) On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.net wrote: Will you be at XML Amsterdam on Wednesday? And will any other people who are on this list be there? On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com wrote: Hi Charles, Excellent suggestion. It's not the usual approach we take to set properties but there's also nothing stopping me from storing XML in Sedna containing properties. Brilliant workaround ;-) Thx, Robby -Original Message- From: charles.fos...@gmail.com [mailto: charles.fos...@gmail.com] On Behalf Of Charles Foster Sent: Thursday, September 13, 2012 12:52 PM To: Robby Pelssers Cc: sedna-discussion@lists.sourceforge.net Subject: Re: [Sedna-discussion] question related to external global variables Hi Robby, XQuery Library Modules (stored in Sedna) [1] can not have external
Re: [Sedna-discussion] question related to external global variables
Oleg, Ilya can you enlighten us on this? :) I definitely don't have enough
information to answer this question.
Is there a new deadline to the Sedna 4.0 release?
On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ru wrote:
We *hope* that we will be able to release aplha version by 10.10.2012 but
it's not a deadline : if something would be broken by that moment we will
not be able to make a release
On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa
flavioso...@ufc.brwrote:
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ru wrote:
Well, it's not ready yet and it's not a guarantee that everything would
work as expected. But we hope that we would be able to make the following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements
for some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong
with one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need
just to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to
hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna is
listening to.
5. It would be possible to start sedna as windows service
natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It
would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes
that would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should
result in better code quality
13. clang/llvm compiler support (it's working now too but we
should check that everything is okay)
I could forget something, but these are common new features that we are
working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ruwrote:
We are working hard on Sedna 4.0 and it's not too simple to have a
trip anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster
char...@cfoster.netwrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in
Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com]
On Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external
global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as
xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module
which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable
like
$base-uri to exist for every single ad-hoc XQuery you invoke, you
will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1]
http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is
environment specific.
declare function rdfutil:getURI($type as xs:string, $id as
xs:string) as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type
Re: [Sedna-discussion] question related to external global variables
We have no deadline and no ideas when exactly we will finish everything. We
have 3 directions to finish still:
1) arch
2) new testing system
3) check that everything works after merge with Ilyas' new optimizer
branch.
Until everything will be checked there's no new release. It's hard to
forecast the time it takes because there is a lot of current interrupting
work on other things. It will be finished for sure but we don't know when
exactly
On Tue, Nov 13, 2012 at 2:00 PM, Ivan Shcheklein shchekl...@gmail.comwrote:
Oleg, Ilya can you enlighten us on this? :) I definitely don't have enough
information to answer this question.
Is there a new deadline to the Sedna 4.0 release?
On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ru wrote:
We *hope* that we will be able to release aplha version by 10.10.2012
but it's not a deadline : if something would be broken by that moment we
will not be able to make a release
On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa
flavioso...@ufc.brwrote:
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ruwrote:
Well, it's not ready yet and it's not a guarantee that everything
would work as expected. But we hope that we would be able to make the
following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements
for some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong
with one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need
just to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to
hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna
is listening to.
5. It would be possible to start sedna as windows service
natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It
would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes
that would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should
result in better code quality
13. clang/llvm compiler support (it's working now too but we
should check that everything is okay)
I could forget something, but these are common new features that we
are working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ruwrote:
We are working hard on Sedna 4.0 and it's not too simple to have a
trip anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.net
wrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in
Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com]
On Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external
global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have
external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as
xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module
which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable
like
$base-uri to exist for every single ad-hoc XQuery you invoke, you
will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps
Re: [Sedna-discussion] question related to external global variables
Hi Sedna Team,
Thanks for your feedback. I'm looking forward for the new release. Good
luck.
Regards,
On Tue, Nov 13, 2012 at 9:28 AM, Олег Борисенко a...@somestuff.ru wrote:
We have no deadline and no ideas when exactly we will finish everything.
We have 3 directions to finish still:
1) arch
2) new testing system
3) check that everything works after merge with Ilyas' new optimizer
branch.
Until everything will be checked there's no new release. It's hard to
forecast the time it takes because there is a lot of current interrupting
work on other things. It will be finished for sure but we don't know when
exactly
On Tue, Nov 13, 2012 at 2:00 PM, Ivan Shcheklein shchekl...@gmail.comwrote:
Oleg, Ilya can you enlighten us on this? :) I definitely don't have
enough information to answer this question.
Is there a new deadline to the Sedna 4.0 release?
On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ru wrote:
We *hope* that we will be able to release aplha version by 10.10.2012
but it's not a deadline : if something would be broken by that moment we
will not be able to make a release
On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa flavioso...@ufc.br
wrote:
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ruwrote:
Well, it's not ready yet and it's not a guarantee that everything
would work as expected. But we hope that we would be able to make the
following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements
for some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong
with one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need
just to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to
hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna
is listening to.
5. It would be possible to start sedna as windows service
natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It
would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes
that would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should
result in better code quality
13. clang/llvm compiler support (it's working now too but we
should check that everything is okay)
I could forget something, but these are common new features that we
are working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко
a...@somestuff.ruwrote:
We are working hard on Sedna 4.0 and it's not too simple to have a
trip anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster
char...@cfoster.net wrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to
set properties but there's also nothing stopping me from storing XML
in
Sedna containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com]
On Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external
global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have
external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as
xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module
which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the
variable
Re: [Sedna-discussion] question related to external global variables
Is there a new deadline to the Sedna 4.0 release?
On Thu, Sep 13, 2012 at 6:59 PM, Олег Борисенко a...@somestuff.ru wrote:
We *hope* that we will be able to release aplha version by 10.10.2012 but
it's not a deadline : if something would be broken by that moment we will
not be able to make a release
On Fri, Sep 14, 2012 at 1:48 AM, Flávio R. C. Sousa flavioso...@ufc.brwrote:
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ru wrote:
Well, it's not ready yet and it's not a guarantee that everything would
work as expected. But we hope that we would be able to make the following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements for
some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong
with one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need just
to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to
hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna is
listening to.
5. It would be possible to start sedna as windows service
natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It
would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes that
would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should result
in better code quality
13. clang/llvm compiler support (it's working now too but we
should check that everything is okay)
I could forget something, but these are common new features that we are
working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ruwrote:
We are working hard on Sedna 4.0 and it's not too simple to have a
trip anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster
char...@cfoster.netwrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com]
On Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as
xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module
which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable
like
$base-uri to exist for every single ad-hoc XQuery you invoke, you
will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is
environment specific.
declare function rdfutil:getURI($type as xs:string, $id as
xs:string) as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set
externally
Re: [Sedna-discussion] question related to external global variables
Ok... meanwhile I did some quick hacking and came up with the following
solution. The idea of storing properties is based on how the
Cocoon-Spring-Configurator searches for properties in the classpath.
http://robbypelssers.blogspot.nl/2012/09/using-properties-from-within-xquery.html
Any improvements or comments are welcome.
Robby
-Original Message-
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Thursday, September 13, 2012 1:17 PM
To: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global variables
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set properties
but there's also nothing stopping me from storing XML in Sedna containing
properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On Behalf Of
Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set externally. (e.g.
$base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is understandable as I
reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as or
external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as xs:string,
$id as xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But this would have to get propagated to ALL functions calling
rdfutil:getURI, which more concretely would involve changing every single
function as they all depend on this rdfutil:getURI (in)directly.
As a side note,
We are using the driver from Charles Foster but that won't help us in this
case as this use case is about modules and not standalone xqueries used in
our app.
So besides the tedious solution of refactoring all function signatures, is
there a simpler way?
Thx in advance,
Robby
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo
Re: [Sedna-discussion] question related to external global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set externally. (e.g.
$base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is understandable as I
reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as or
external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as xs:string,
$id as xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But this would have to get propagated to ALL functions calling
rdfutil:getURI, which more concretely would involve changing every single
function as they all depend on this rdfutil:getURI (in)directly.
As a side note,
We are using the driver from Charles Foster but that won't help us in this
case as this use case is about modules and not standalone xqueries used in
our app.
So besides the tedious solution of refactoring all function signatures, is
there a simpler way?
Thx in advance,
Robby
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
Re: [Sedna-discussion] question related to external global variables
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set properties
but there's also nothing stopping me from storing XML in Sedna containing
properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On Behalf Of
Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set externally. (e.g.
$base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string) as
xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is understandable as I
reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as or
external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as xs:string,
$id as xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But this would have to get propagated to ALL functions calling
rdfutil:getURI, which more concretely would involve changing every single
function as they all depend on this rdfutil:getURI (in)directly.
As a side note,
We are using the driver from Charles Foster but that won't help us in this
case as this use case is about modules and not standalone xqueries used in
our app.
So besides the tedious solution of refactoring all function signatures, is
there a simpler way?
Thx in advance,
Robby
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
Re: [Sedna-discussion] question related to external global variables
We are working hard on Sedna 4.0 and it's not too simple to have a trip
anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.net wrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On
Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set externally.
(e.g. $base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is understandable
as I reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as or
external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as
xs:string, $id as xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But this would have to get propagated to ALL functions calling
rdfutil:getURI, which more concretely would involve changing every single
function as they all depend on this rdfutil:getURI (in)directly.
As a side note,
We are using the driver from Charles Foster but that won't help us in
this case as this use case is about modules and not standalone xqueries
used in our app.
So besides the tedious solution of refactoring all function signatures,
is there a simpler way?
Thx in advance,
Robby
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the latest in
malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
Re: [Sedna-discussion] question related to external global variables
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ru wrote:
We are working hard on Sedna 4.0 and it's not too simple to have a trip
anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.netwrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On
Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set externally.
(e.g. $base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is understandable
as I reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as or
external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as
xs:string, $id as xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But this would have to get propagated to ALL functions calling
rdfutil:getURI, which more concretely would involve changing every single
function as they all depend on this rdfutil:getURI (in)directly.
As a side note,
We are using the driver from Charles Foster but that won't help us in
this case as this use case is about modules and not standalone xqueries
used in our app.
So besides the tedious solution of refactoring all function
signatures, is there a simpler way?
Thx in advance,
Robby
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the latest in
malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the latest in
malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https
Re: [Sedna-discussion] question related to external global variables
Well, it's not ready yet and it's not a guarantee that everything would
work as expected. But we hope that we would be able to make the following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements for
some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong with
one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need just to
connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to hang
sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna is
listening to.
5. It would be possible to start sedna as windows service natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It would
result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes that
would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should result in
better code quality
13. clang/llvm compiler support (it's working now too but we should
check that everything is okay)
I could forget something, but these are common new features that we are
working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.comwrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ru wrote:
We are working hard on Sedna 4.0 and it's not too simple to have a trip
anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.netwrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On
Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set
externally. (e.g. $base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is
understandable as I reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as
or external
I could of course change the function signature to
declare function rdfutil:getURI($base_uri as xs:string, $type as
xs:string, $id as xs:string) as xs:anyURI
Re: [Sedna-discussion] question related to external global variables
Hi Олег,
I was wondering what new protocol is going to ship with Sedna 4.0 and
if it will be backward compatible with the Sedna 3.0 and 4.0 protocols
[1] ?
Kind Regards,
Charles
[1] http://www.sedna.org/serverprotocol/ClientServerProtocol.html
On 13 September 2012 22:24, Олег Борисенко a...@somestuff.ru wrote:
Well, it's not ready yet and it's not a guarantee that everything would work
as expected. But we hope that we would be able to make the following:
New numbering scheme. It should result in much smaller disk utilization.
Query optimizer. It should result in performance improvements for some types
of queries.
Reduction of semaphores usage.
Database wouldn't depend one on another. It something is wrong with one
database, it wouldn't crash others.
New front-end architecture:
Database management become client-side --- you would need just to connect
se_gov to create/delete/start/stop databases
Asynchronious messaging protocol: it would be impossible to hang sedna
from outside
No need for pping
It would be possible to specify many interfaces that sedna is listening to.
It would be possible to start sedna as windows service natively.
New protocol
Pool of trn's: se_trn wouldn't die after each session. It would result in
much faster small transactions.
(maybe) diagnostic messaging channel for se_trn processes that would
indicate transactions progress.
(maybe not in v4.0 but v4.1) rest api
(maybe not in v4.0 but v4.1) some sort of embedded sedna
(maybe) openssl library for connections encryption
internal unit-tests and new testing system that should result in better code
quality
clang/llvm compiler support (it's working now too but we should check that
everything is okay)
I could forget something, but these are common new features that we are
working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa flaviocso...@gmail.com
wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ru wrote:
We are working hard on Sedna 4.0 and it's not too simple to have a trip
anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.net
wrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On
Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants =
http://http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is environment
specific.
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set
externally. (e.g. $base_uri)
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is
understandable as I reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as
or external
Re: [Sedna-discussion] question related to external global variables
Very cool. Do you have some deadline to released?
On Thu, Sep 13, 2012 at 6:24 PM, Олег Борисенко a...@somestuff.ru wrote:
Well, it's not ready yet and it's not a guarantee that everything would
work as expected. But we hope that we would be able to make the following:
1. New numbering scheme. It should result in much smaller disk
utilization.
2. Query optimizer. It should result in performance improvements for
some types of queries.
3. Reduction of semaphores usage.
4. Database wouldn't depend one on another. It something is wrong with
one database, it wouldn't crash others.
5. New front-end architecture:
1. Database management become client-side --- you would need just
to connect se_gov to create/delete/start/stop databases
2. Asynchronious messaging protocol: it would be impossible to
hang sedna from outside
3. No need for pping
4. It would be possible to specify many interfaces that sedna is
listening to.
5. It would be possible to start sedna as windows service natively.
6. New protocol
7. Pool of trn's: se_trn wouldn't die after each session. It
would result in much faster small transactions.
8. (maybe) diagnostic messaging channel for se_trn processes that
would indicate transactions progress.
9. (maybe not in v4.0 but v4.1) rest api
10. (maybe not in v4.0 but v4.1) some sort of embedded sedna
11. (maybe) openssl library for connections encryption
12. internal unit-tests and new testing system that should result
in better code quality
13. clang/llvm compiler support (it's working now too but we should
check that everything is okay)
I could forget something, but these are common new features that we are
working on :)
On Thu, Sep 13, 2012 at 9:14 PM, Flávio R. C. Sousa
flaviocso...@gmail.com wrote:
What's new features in Sedna 4.0 ?
On Thu, Sep 13, 2012 at 1:06 PM, Олег Борисенко a...@somestuff.ru wrote:
We are working hard on Sedna 4.0 and it's not too simple to have a trip
anywhere at this moment :)
On Thu, Sep 13, 2012 at 5:29 PM, Charles Foster char...@cfoster.netwrote:
Will you be at XML Amsterdam on Wednesday?
And will any other people who are on this list be there?
On 13 September 2012 12:16, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi Charles,
Excellent suggestion. It's not the usual approach we take to set
properties but there's also nothing stopping me from storing XML in Sedna
containing properties.
Brilliant workaround ;-)
Thx,
Robby
-Original Message-
From: charles.fos...@gmail.com [mailto:charles.fos...@gmail.com] On
Behalf Of Charles Foster
Sent: Thursday, September 13, 2012 12:52 PM
To: Robby Pelssers
Cc: sedna-discussion@lists.sourceforge.net
Subject: Re: [Sedna-discussion] question related to external global
variables
Hi Robby,
XQuery Library Modules (stored in Sedna) [1] can not have external
variables.
Only XQuery Main Modules (i.e. Ad-hoc queries) can have external
variables, you can bind these from the XQJ driver.
You could set a constant variable in an XQuery Library Module.
e.g.
import module namespace constants = http://
http://prod.nxp.com/constants;;
declare function rdfutil:getURI($type as xs:string, $id as xs:string)
as xs:anyURI {
xs:anyURI(concat($constants:base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
If you want flexibility, you could have an XQuery Library Module which
provided functions to read values (like a base-uri) from a XML
document existing in the Database.
If you want to import no library module AND want for the variable like
$base-uri to exist for every single ad-hoc XQuery you invoke, you will
need to declare an external variable and bind via XQExpression or
XQPreparedExpression.
Hope this helps.
Regards,
Charles
[1] http://www.sedna.org/progguide/ProgGuidesu8.html#x14-570002.5.5
On 13 September 2012 11:15, Robby Pelssers robby.pelss...@nxp.com
wrote:
Hi all,
I've read that Sedna does not support external variables
http://www.sedna.org/progguide/ProgGuidesu4.html
But I have a function that needs to return a URI which is
environment specific.
declare function rdfutil:getURI($type as xs:string, $id as
xs:string) as xs:anyURI {
xs:anyURI(concat(http://prod.nxp.com;, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
So ideally I want to use a global variable which I can set
externally. (e.g. $base_uri)
declare function rdfutil:getURI($type as xs:string, $id as
xs:string) as xs:anyURI {
xs:anyURI(concat($base_uri, /id/, $type, /,
rdfutil:normalizeIdentifier($id)))
};
But Sedna won't allow me to deploy this module which is
understandable as I reference a non declared variable
Details: at (10:35), syntax error, unexpected ;, expecting := or as
or external
