Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com
 designates 209.85.212.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=UJoKV2amwAWVP43gK5gZyqcmKZ/XkXquqH45KcpTNh20oWTiQrbw5cR18O+h05/LRn
         XEa+UP5GaXD0ePXmGOgnASgF0QwnS01Jl15N0Z/7cwjkOTNSW/LVACrznBuyWRhIBbhR
         Q5BZYhjk6hivclclB8O9E23+wiG6+EDQ16lAA=
Message-ID: <4BB3554B.9050105@gmail.com>
Date: Wed, 31 Mar 2010 06:59:39 -0700
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Data type compatibility
References: <93d36c111003270425v6ac9d388t3278b0cd2a0e9e4e@mail.gmail.com>
	 <4BB0B654.2060907@gmail.com>
	 <93d36c111003300246t34ac1e5vdae60e094fa340fe@mail.gmail.com>
	 <4BB20762.8050403@gmail.com>
 <k2g93d36c111003310450h6eb61fa7q1a29cf18ee293cf6@mail.gmail.com>
In-Reply-To: <k2g93d36c111003310450h6eb61fa7q1a29cf18ee293cf6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

?? ??????????? wrote:
> So, you feeling OK about sending such a proposal to Google guys? They 
> will forward to Apache people, so I will post proposal to derby-dev 
> mailing list also for conversation in community

That sounds good to me. It's important that all technical discussions about
Derby's implementations happen as a conversation in the community, so
derby-dev is the right place to discuss the issues around building SQLXML support.

Your GSoC application can, and should, refererence the derby-dev mail threads
and the JIRA issues that are used for tracking work for the project. As we
start to get more specific about the particular aspects of JDBC/SQLXML support
that need to be implemented, we can open specific JIRA entries to track each one.

As you can see, there are a number of existing JIRA entries about the XML support
that has been added so far, for example:
  - https://issues.apache.org/jira/browse/DERBY-688
  - https://issues.apache.org/jira/browse/DERBY-1759
Studying these issues in detail should give you a feel for how the process
of developing additional SQLXML support can proceed: identify the areas where
Derby's support is lacking, propose an implementation to enhance Derby in those
areas, respond to community comments and suggestions, develop tests, etc.

Your ideas about the uses of XML and extensions to the XML handling are
great. The most important thing for the Derby community is to implement
a standards-compliant and highly-compatible database, so our first priority
is to ensure that we implement the JDBC and SQLXML specs, but beyond that
we can propose extensions to the XML handling to the Derby community to
see what the reaction is.

It is great that you have looked into the implementations of SQLXML in
Postgres, MySQL, and others; since the goal is compatibility, it will be
very helpful to compare our implementation against others.

Great work getting this far! I think the next step is for you to put together
a GSoC application and be as specific as you can be about the proposed work.

thanks,

bryan