<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>John Sublett's Blog</title>
<link>http://www.niagara-central.com:80/ord?portal:/blog/Blog/7</link>
<description>John Sublett's Blog</description>
<item>
 <title>BQL Demystified - Part I</title>
 <link>http://www.niagara-central.com:80/ord?portal:/blog/BlogEntry/103</link>
 <guid>http://www.niagara-central.com:80/ord?portal:/blog/BlogEntry/103</guid>
 <pubDate>Wed, 11 Apr 2007 18:05:57 EDT</pubDate>
 <description><![CDATA[<p>Posted by John Sublett</p><p>BQL is already a powerful tool for querying several different data sources
in Niagara including component data, alarms, and histories.  There is
some documentation available in the docDeveloper module that is
worth a read.  It includes a nice high level view of BQL syntax and lots
of examples.  While examples are always nice, and more are always better,
you can really only get so far with examples.  Eventually
you'll come across a problem that isn't covered by an example and if you
don't understand how it works, you're out of luck.  My goal here is to
provide a better understanding of the mechanics of how a BQL query is
evaluated so that when you have that report you're building that
keeps you coming back to the brute force approach or pulling your hair out,
you will naturally think BQL instead.</p>]]></description>
</item>
<item>
 <title>Welcome To Niagara Central</title>
 <link>http://www.niagara-central.com:80/ord?portal:/blog/BlogEntry/38</link>
 <guid>http://www.niagara-central.com:80/ord?portal:/blog/BlogEntry/38</guid>
 <pubDate>Mon, 31 Jul 2006 13:40:57 EDT</pubDate>
 <description><![CDATA[<p>Posted by John Sublett</p><p>The Niagara community is growing fast and it's made up of some pretty
diverse groups including systems integrators, app developers, appliance developers, and end users, just to name a few.  With all of these creative people in the mix, the Niagara Framework has truly taken on a life of its own.  The entire purpose of Niagara Central is to support the growing community and bring people together to facilitate exchange of knowledge and ideas.</p>]]></description>
</item>
</channel>
</rss>
