Gsoc XQuery

*IDEA:XMLQuery*

* *

*Abstract*

SQL/XML makes it possible to store your XML documents in your SQL database,
to query those documents using XPath and XQuery, and to "publish" your
existing SQL data in the form of XML documents.

*Benefits of Project*

SQL/XML is an ANSI and ISO standard that provides support for using XML in
the context of an SQL database system. Because SQL is the standard language
for accessing and managing data stored in relational databases, it is
natural that enterprises and users worldwide need the ability to integrate
their XML data into their relational data through the use of SQL
facilities.SQL/XML makes it possible to store your XML documents in your SQL
database, to query those documents using XPath and XQuery, and to "publish"
your existing SQL data in the form of XML documents.

Nowadays Xml datatype is generally used to store,manipulate and export data
between cross-platforms.We intend to implement and XML/SQL query for the
postgresql based on XQuery,XPath. Postgresql 8.3 implemetns core
functionalities for the SQL/XML but the XQuery is still needed to supported.
Since XML is semi-structured it is flexible to use by other programming
languages,reporting web-based applications as well as data exchange between
different DBMSs.

*Delivarables on Timeline*

The implementation of XQuery support can ce achieved by;

*Understanding the basics of the SQL/XML (1 week)

*A research of on other kinds of XQuery supported DBMSs scuh as; Oracle and
SQLServer(1-2 week)

*The design for the core functionalities of the XQuery (2-4 week)

*First few hard-coded functionalities(1-2 week)

*Testing and adding more details during an iterative development(1-2 week)

*Implementation of a GUI for XQuery for the PostgreSql users (2 week)

*Final tests and documentation (1-2 week)

*About me*

I am a senior student at computer engineering at
iztech<http://english.iyte.edu.tr/main_eng.jsp?pageName=main.htm> in
turkey. My areas of inetrests are information management, OOP(Object
Oriented Programming) and currently bioinformatics. I have been working with
a Asistan Professor(Jens Allmer <http://jens.allmer.de/>) in molecular
biology genetics department for one year.Firstly, we worked on a protein
database 2DB <http://www.2db.de.ms/> and we presented the project in
HIBIT09<http://hibit09.ii.metu.edu.tr/>organization. The
Project was “Database management system independence by amending 2DB with a
database access layer”. Currently, I am working on another project (Kerb) as
my senior project which is a general sqeuential task management system
intend to reduce the errors and increase time saving in biological
experiments. We will present this project in
HIBIT2010<http://hibit2010.ii.metu.edu.tr/> too.
Moreover,I am good at data structures and implementations on C.

Contact: e-mails; necatibatur(at)gmail(dot)com ,

Necati Batur wrote:
>
> *IDEA:XMLQuery*
>
> * *
>
> *Abstract*
>
> SQL/XML makes it possible to store your XML documents in your SQL
> database, to query those documents using XPath and XQuery, and to
> "publish" your existing SQL data in the form of XML documents.
>
> *Benefits of Project*
>
> SQL/XML is an ANSI and ISO standard that provides support for using
> XML in the context of an SQL database system. Because SQL is the
> standard language for accessing and managing data stored in relational
> databases, it is natural that enterprises and users worldwide need the
> ability to integrate their XML data into their relational data through
> the use of SQL facilities.SQL/XML makes it possible to store your XML
> documents in your SQL database, to query those documents using XPath
> and XQuery, and to "publish" your existing SQL data in the form of XML
> documents.
>
> Nowadays Xml datatype is generally used to store,manipulate and export
> data between cross-platforms.We intend to implement and XML/SQL query
> for the postgresql based on XQuery,XPath. Postgresql 8.3 implemetns
> core functionalities for the SQL/XML but the XQuery is still needed to
> supported. Since XML is semi-structured it is flexible to use by other
> programming languages,reporting web-based applications as well as data
> exchange between different DBMSs.
>
> *Delivarables on Timeline*
>
> The implementation of XQuery support can ce achieved by;
>
> *Understanding the basics of the SQL/XML (1 week)
>
> *A research of on other kinds of XQuery supported DBMSs scuh as;
> Oracle and SQLServer(1-2 week)
>
> *The design for the core functionalities of the XQuery (2-4 week)
>
> *First few hard-coded functionalities(1-2 week)
>
> *Testing and adding more details during an iterative development(1-2 week)
>
> *Implementation of a GUI for XQuery for the PostgreSql users (2 week)
>
> *Final tests and documentation (1-2 week)
>
> *About me*
>
> I am a senior student at computer engineering at iztech
> <http://english.iyte.edu.tr/main_eng.jsp?pageName=main.htm> in turkey.
> My areas of inetrests are information management, OOP(Object Oriented
> Programming) and currently bioinformatics. I have been working with a
> Asistan Professor(Jens Allmer <http://jens.allmer.de/>) in molecular
> biology genetics department for one year.Firstly, we worked on a
> protein database 2DB <http://www.2db.de.ms/> and we presented the
> project in HIBIT09 <http://hibit09.ii.metu.edu.tr/>organization. The
> Project was “Database management system independence by amending 2DB
> with a database access layer”. Currently, I am working on another
> project (Kerb) as my senior project which is a general sqeuential task
> management system intend to reduce the errors and increase time saving
> in biological experiments. We will present this project in HIBIT2010
> <http://hibit2010.ii.metu.edu.tr/> too. Moreover,I am good at data
> structures and implementations on C.
>

Have you reviewed the discussions that have already occurred regarding
XQuery?

See for example here:
<http://archives.postgresql.org/pgsql-hackers/2010-02/msg01350.php> and
following emails in the thread.

This is not something to be done in isolation.

(Personally I wish some SOC student would do LATERAL. It would be useful
and is a feature of about the right size, I think).

cheers

andrew

On Fri, Apr 9, 2010 at 4:37 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> (Personally I wish some SOC student would do LATERAL. It would be useful and
> is a feature of about the right size, I think).

Actually, I think that requires two rounds of significant executor
refactoring. This is round two:

http://archives.postgresql.org/pgsql-hackers/2009-10/msg00994.php

Round one, which Tom said he was already planning to do for 9.1, is to
eliminate the hack by which "outer tuples" are passed down into
nest-loops-with-inner-indexscan. Once those two things are done the
remaining work might be suitable for a GSoC project.

...Robert

Necati Batur escribió:

> *Delivarables on Timeline*
>
> The implementation of XQuery support can ce achieved by;
>
> *Understanding the basics of the SQL/XML (1 week)
>
> *A research of on other kinds of XQuery supported DBMSs scuh as; Oracle and
> SQLServer(1-2 week)
>
> *The design for the core functionalities of the XQuery (2-4 week)
>
> *First few hard-coded functionalities(1-2 week)
>
> *Testing and adding more details during an iterative development(1-2 week)
>
> *Implementation of a GUI for XQuery for the PostgreSql users (2 week)

What, you will *also* implement a GUI? Gimme a break. There's no way
you can achieve most of these in "1-2 weeks". Are you Tom Lane
perchance?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

On Fri, Apr 9, 2010 at 5:02 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Necati Batur escribió:
>
>> *Delivarables on Timeline*
>>
>> The implementation of XQuery support can ce achieved by;
>>
>> *Understanding the basics of the SQL/XML (1 week)
>>
>> *A research of on other kinds of XQuery supported DBMSs scuh as; Oracle and
>> SQLServer(1-2 week)
>>
>> *The design for the core functionalities of the XQuery (2-4 week)
>>
>> *First few hard-coded functionalities(1-2 week)
>>
>> *Testing and adding more details during an iterative development(1-2 week)
>>
>> *Implementation of a GUI for XQuery for the PostgreSql users (2 week)
>
> What, you will *also* implement a GUI?  Gimme a break.  There's no way
> you can achieve most of these in "1-2 weeks".  Are you Tom Lane
> perchance?

I think the problem with this and the other proposal from the same
student is that, according to his submissions and statements, he
doesn't really know what the design for any of these features is going
to be. So his plan is to first figure out the design, and then
implement it. I don't believe he's done any work reading through
existing mailing list discussions, wiki pages, or even maybe our core
documentation. I believe we should really be expecting students to
have a fairly detailed design at the time they submit the project -
the summer is for implementing it, not for figuring out what "it" is
and then implementing it.

This might be just barely acceptable if he started with a small
project for which we already pretty much know what the design has to
be. But for a major undertaking like the two he's proposed so far,
you can't think that you're going to start with hand-waving and end up
with something useful.

...Robert

On Fri, Apr 9, 2010 at 5:02 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Necati Batur escribió:
>
>> *Delivarables on Timeline*
...
>> *Implementation of a GUI for XQuery for the PostgreSql users (2 week)
>
> What, you will *also* implement a GUI?  Gimme a break.  There's no way
> you can achieve most of these in "1-2 weeks".  Are you Tom Lane
> perchance?

Indeed. I've learned it's not a good idea to throw a GUI into a
proposal when the rest of the project is already substantial, as it
can lead to embarrassment when it doesn't get realized ;-) I did that
last year.