On Mon, Nov 2, 2009 at 11:34 AM, Amit Nithian wrote:
> A thought I had on this from a DIH design perspective. Would it be better to
> have the SQL queries stored in an element rather than an attribute so that
> you can wrap it in a CDATA block without having to mess up the look of query
> with <,
A thought I had on this from a DIH design perspective. Would it be better to
have the SQL queries stored in an element rather than an attribute so that
you can wrap it in a CDATA block without having to mess up the look of query
with <, >? Makes debugging easier (I know find and replace is trivial
It is easier to put SQL select statements in a view, and just use that
view from the DIH configuration file.
On Tue, Oct 27, 2009 at 12:30 PM, Andrew Clegg wrote:
>
>
> Heh, eventually I decided
>
> "where 4 > node_depth"
>
> was the most pleasing (if slightly WTF-ish) way of writing it...
>
> Ch
Heh, eventually I decided
"where 4 > node_depth"
was the most pleasing (if slightly WTF-ish) way of writing it...
Cheers,
Andrew.
Erik Hatcher-4 wrote:
>
> Use < instead of < in that attribute. That should fix the issue.
> Remember, it's an XML file, so it has to obey XML encoding rule
Use < instead of < in that attribute. That should fix the issue.
Remember, it's an XML file, so it has to obey XML encoding rules which
make it ugly but whatcha gonna do?
Erik
On Oct 27, 2009, at 11:50 AM, Andrew Clegg wrote:
Hi,
If I have a DataImportHandler query with a great
