Re: Generating SQL statements in BL

--===============0660533075==
Content-Type: multipart/signed; micalg=SHA1;
	boundary="Sig_/IMXrNu0n.dwlGXO842qXXSP";
	protocol="application/pkcs7-signature"

--Sig_/IMXrNu0n.dwlGXO842qXXSP
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon 12-Oct-2009 20:24
"[email protected]" <[email protected]> wrote:

> The tableddl scenario goes a step in this direction, but it is
> limited to the CREATE statements that create a Xaraya installation.
> This idea would allow us to generalize the approach in that scenario.

That it does 'CREATE' statements (or 'ALTER' as we see fit) is more or
less unrelated to the xml. The DTD describes a set of elements
describing tables, columns and what have you; declarative in any case.

The DDL code then takes its turn and transforms these declarations into
other declarations specified not in XML but in SQL. They fit nicely
because they both declare things (almost staticallly).

If you get into the /querying/ part of SQL, the distance increases from
the declarative nature of XML, making it harder.=20

The usual solution would be to add another layer to the cake which can
cross that distance. In some way, our modules are such a layer. They
(can) add behaviour on top of the DD objects they use and optionally add
tags at their own abstraction layer.=20

marcel

--=20
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV    -- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build          -- http://cobra.mrblog.nl

--Sig_/IMXrNu0n.dwlGXO842qXXSP--


--===============0660533075==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xaraya_devel mailing list
[email protected]
http://xaraya.com/mailman/listinfo/xaraya_devel

--===============0660533075==--