<?xml version="1.0" encoding="utf-8"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Ingres Community Forums - Blogs - stephenb</title>
		<link>http://community.ingres.com/forum/blogs/stephenb/</link>
		<description><![CDATA[Ingres Corporation is a leading provider of open source database management software and support services. [Toll Free] +1 (888) 446-4737]]></description>
		<language>en</language>
		<lastBuildDate>Tue, 09 Feb 2010 15:27:40 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://community.ingres.com/forum/ingres4/misc/rss.jpg</url>
			<title>Ingres Community Forums - Blogs - stephenb</title>
			<link>http://community.ingres.com/forum/blogs/stephenb/</link>
		</image>
		<item>
			<title><![CDATA[What's happening in the DBMS group]]></title>
			<link>http://community.ingres.com/forum/blogs/stephenb/4-whats-happening-dbms-group.html</link>
			<pubDate>Wed, 10 Jun 2009 06:00:55 GMT</pubDate>
			<description><![CDATA[I thought a blog might be a good way of letting people know what's happening with the Ingres DBMS, and hopefully we can get some feedback. So here...]]></description>
			<content:encoded><![CDATA[<div>I thought a blog might be a good way of letting people know what's happening with the Ingres DBMS, and hopefully we can get some feedback. So here are some of the things we're working on right now:<br />
<br />
<ul><li>MVCC - For those that aren't familiar with this acronym, it stands for Multi-version Concurrency Control. It adds the ability for the DBMS to create multiple versions of the same data in a controlled fashion, allowing readers to see the old version of a piece of data as of a given point-in-time; this allows for consistent reads without locks, if another thread updates a page, they simply create a new version of it and the reader continues to read the old version. Once the data is committed the reader may see it or not, based on the point-in-time of their consistent read. So readers don't block writers (and vice-versa), making it a very powerful feature for OLTP since it increases concurrency tremendously. See here for details on that we're doing (<a href="http://community.ingres.com/wiki/MVCC" target="_blank">http://community.ingres.com/wiki/MVCC</a>)</li>
<li>data at rest encryption (column based) - this is something we need for a number of standards, and it significantly enhances our security story. MikeT is the point man on this, check out the project page here (<a href="http://community.ingres.com/wiki/Data_at_Rest_Encryption" target="_blank">http://community.ingres.com/wiki/Dat...est_Encryption</a>)</li>
<li>support for long object names - This feature will help us port third party partner applications to Ingres. Some other vendors support longer object names than Ingres, and it causes a lot of porting work in certain applications. The current thought is that we will support object names up to 128 bytes (number of actual characters may vary if you're using UTF8 or DBCS). This feature is available in the source now and can be built with a special flag if anyone wants to try it out. We'd really love to get feedback on how this affects existing users and interfaces. e.g. what happens when you try to access a table with a long name from an ABF application. You can check you the details here (<a href="http://community.ingres.com/wiki/Long_Identifiers" target="_blank">http://community.ingres.com/wiki/Long_Identifiers</a>)</li>
<li>scalar sub-queries - this feature allows you to use other queries within the &quot;SELECT&quot; cause of a query. We have this in a limited form already; this project will implement full ANSI compliance for this feature. The project has just started, so there's not much to say, but you can follow the progress here (<a href="http://community.ingres.com/wiki/Scalar_Subqueries" target="_blank">http://community.ingres.com/wiki/Scalar_Subqueries</a>)</li>
<li>Better error handling for offline recovery - some parts of this feature are in Ingres 9.2 (unsupported) and we plan to round it off in the next release and support it properly. Details are here (<a href="http://community.ingres.com/wiki/RCP_Offline_Redo_Undo_Error_Handling" target="_blank">http://community.ingres.com/wiki/RCP...Error_Handling</a>)</li>
</ul>There are a bunch of other things in the works which I'll try to talk about in the next post. <br />
<br />
You also might be interested in the DBMS features some community members are working on. Marty Bowes is close to being ready with his check digit functions, see here (<a href="http://community.ingres.com/wiki/Check_Digit_Functions" target="_blank">http://community.ingres.com/wiki/Check_Digit_Functions</a>). Karl Schendel is working on a bunch of things, including build system improvements (<a href="http://community.ingres.com/wiki/Build_system_improvements_for_better_parameterization" target="_blank">http://community.ingres.com/wiki/Bui...rameterization</a>) and partitioned global temporary tables (<a href="http://community.ingres.com/wiki/Partitioned_global_temporary_tables" target="_blank">http://community.ingres.com/wiki/Par...mporary_tables</a>).<br />
<br />
I'm also trying to bootstrap a project to improve the performance of LOBs by inlining them into the base table (and getting rid of the etab). We need this for our geospatial work (<a href="http://community.ingres.com/wiki/IngresGeospatial" target="_blank">http://community.ingres.com/wiki/IngresGeospatial</a>), but it would be generally useful to anyone using LOBs extensively . I have designed a prototype; if anyone wants to help me code it just drop me a note.</div>

]]></content:encoded>
			<dc:creator>stephenb</dc:creator>
			<dc:publisher>175</dc:publisher>
			<guid isPermaLink="true">http://community.ingres.com/forum/blogs/stephenb/4-whats-happening-dbms-group.html</guid>
		</item>
	</channel>
</rss>
