<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Technical Blog</title>
    <link>https://grep.elasticpath.com/community/techblog/blog</link>
    <description />
    <pubDate>Tue, 15 Sep 2009 23:47:51 GMT</pubDate>
    <generator>Clearspace 2.5.7 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-09-15T23:47:51Z</dc:date>
    <item>
      <title>Elastic Path with Oracle RAC</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/09/16/elastic-path-with-oracle-rac</link>
      <description>The performance team at Elastic Path has recently gone through Oracle RAC validation with Elastic Path 6.1.1 and made it out the other side unscathed. And the best part, is that there are no code changes required on EP out-of-the-box to fully support</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">failover</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">oracle</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">rac</category>
      <pubDate>Wed, 16 Sep 2009 22:21:58 GMT</pubDate>
      <author>alan.schroder@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/09/16/elastic-path-with-oracle-rac</guid>
      <dc:date>2009-09-16T22:21:58Z</dc:date>
      <clearspace:dateToText>2 years, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/elastic-path-with-oracle-rac</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1082</wfw:commentRss>
    </item>
    <item>
      <title>How to display a large product list via JPA native queries</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/05/07/how-to-display-a-large-product-list-via-jpa-native-queries</link>
      <description>We had a client who needed to display entire product categories (several hundred products in all) in a set of drop down list boxes on their Elastic Path Commerce storefront homepage. The data that had to be loaded was quite minimal, just the product</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">native_queries</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">caching</category>
      <pubDate>Thu, 07 May 2009 18:14:58 GMT</pubDate>
      <author>ken.chui@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/05/07/how-to-display-a-large-product-list-via-jpa-native-queries</guid>
      <dc:date>2009-05-07T18:14:58Z</dc:date>
      <clearspace:dateToText>2 years, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/how-to-display-a-large-product-list-via-jpa-native-queries</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1061</wfw:commentRss>
    </item>
    <item>
      <title>Purging customer session records from the database</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/01/27/purging-customer-session-records-from-the-database</link>
      <description>In order to maintain persistent shopping carts and wish lists, EP stores session data as customers shop.  Without maintenance, the database tables will grow over time and may lead to performance problems when customers re-visit the site as the system</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">purge</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">table</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">session</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">cart</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maintenance</category>
      <pubDate>Tue, 27 Jan 2009 21:20:45 GMT</pubDate>
      <author>andrew.naiberg@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/01/27/purging-customer-session-records-from-the-database</guid>
      <dc:date>2009-01-27T21:20:45Z</dc:date>
      <clearspace:dateToText>3 years, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/purging-customer-session-records-from-the-database</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1030</wfw:commentRss>
    </item>
    <item>
      <title>Adding Custom Settings with the EP6.1 Settings Framework</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/01/20/adding-custom-settings-with-the-ep61-settings-framework</link>
      <description>Elastic Path 6.1 provides a new way to manage your application configuration. In the past, settings were stored in a variety of places throughout the system; some were in XML files, others were in properties files, and still others were stored in</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.1</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">configuration</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">api</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">value</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">custom</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">setting</category>
      <pubDate>Tue, 20 Jan 2009 19:39:55 GMT</pubDate>
      <author>daniel.wu@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/01/20/adding-custom-settings-with-the-ep61-settings-framework</guid>
      <dc:date>2009-01-20T19:39:55Z</dc:date>
      <clearspace:dateToText>3 years, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/adding-custom-settings-with-the-ep61-settings-framework</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1024</wfw:commentRss>
    </item>
    <item>
      <title>Upgrading from EP6.0.4 to EP6.1</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2008/11/27/upgrading-from-ep604-to-ep61</link>
      <description>       Elastic Path Commerce 6.1 introduces a number of changes from version 6.0.x.   Primary among these are a major change to the store asset directory structure; movement of store configuration information from the file system to the database; and a</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.0</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.1</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">asset</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">upgrade</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">configuration</category>
      <pubDate>Thu, 27 Nov 2008 22:58:12 GMT</pubDate>
      <author>daniel.wu@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2008/11/27/upgrading-from-ep604-to-ep61</guid>
      <dc:date>2008-11-27T22:58:12Z</dc:date>
      <clearspace:dateToText>3 years, 2 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/upgrading-from-ep604-to-ep61</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1010</wfw:commentRss>
    </item>
    <item>
      <title>Database Schema Changes between EP6.0 and 6.1</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2008/11/27/database-schema-changes-between-ep60-and-61</link>
      <description>There were a number of changes to the database schema in Elastic Path 6.1 compared to the schema in Elastic Path 6.0.4. Some new tables and columns were added to support new functionality, one table that is no longer used was removed, and a few columns</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.0</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.1</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">schema</category>
      <pubDate>Thu, 27 Nov 2008 22:38:39 GMT</pubDate>
      <author>tom.manning@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2008/11/27/database-schema-changes-between-ep60-and-61</guid>
      <dc:date>2008-11-27T22:38:39Z</dc:date>
      <clearspace:dateToText>3 years, 2 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/database-schema-changes-between-ep60-and-61</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1007</wfw:commentRss>
    </item>
  </channel>
</rss>


