Hi, the main drawback I see on storing all your xsl files on a database is that
you
would need a specific application to retrieve the data inside the stylesheets
(by
querying the database, converting the query result into flat files etc)and
being able to
edit your files. For instance, you could store your xsl files info into text
fields in
an SQL Server table and have the advantage of the backup system, but you would
have to
work on the retrieving of the data, by querying the database and managing the
results to
be able to work/edit the stylesheet in, for example, XMLSpy.
I would suggest for better version control of the stylesheets to use tools like
Visual
Source Safe and keeping the info in flat files.
hth,
lizet
Mensaje citado por "Lee, Insoo" <Insoo(_dot_)Lee(_at_)gs(_dot_)com>:
Hi -
Some of my colleagues are considering putting in all xsl stylesheet into
database rather than a flat file.
They want to read in a correct stylesheet on the fly and feed it into
transformer engine as a string.
I think it is a bad idea, but can not come up with a good reason.
Any of you tried to put xsl stylesheets in the database? any reason we
should or should not do it?
Thanks
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
-------------------------------------------------
Este mensaje fue enviado usando el servicio de correo en web de Infomed
http://webmail.sld.cu
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list