From: <liv...@po...> - 2013-01-26 15:56:06
|
>>One example is that we have bar generation queries (N minute intervals). The bar generation logic is complex and depends on numerous domain rules and filter conditions. These rules are defined in xml format and carries a name. While making >>queries, user can specify to generate bar data on a table and also specify which rule files to be used (one or more). >>>As you see I cannot achieve this through standard SQL statement unless I port all the logic to SQL which is also not possible when multiple rule files are involved. There are so many things that my application does but I cannot represent them in >>standard SQL. I want to pass these rules as "HINT"s to my application without breaking the SQL syntax. >>Hope this helps. You can store config info in db not in xml – what problem? You can do import xml into db Read xml by udf, client software and more ... I have one implementation where i read file by udf(especially xml, ini files from some external storage) and read xml as blob and on client side decide what to do i have also simple import feature xml into db as tree structure with attributes – very simple.. implementations should be simplest as possible regards, Karol Bieniaszeski |