You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2017/08/24 01:24:43 UTC
svn commit: r1805989 -
/ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html
Author: dmagda
Date: Thu Aug 24 01:24:43 2017
New Revision: 1805989
URL: http://svn.apache.org/viewvc?rev=1805989&view=rev
Log:
fixed the header
Modified:
ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html
Modified: ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html?rev=1805989&r1=1805988&r2=1805989&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html (original)
+++ ignite/site/trunk/use-cases/comparison/ignite-for-rdbms.html Thu Aug 24 01:24:43 2017
@@ -65,7 +65,7 @@ under the License.
Ignite can store data and indexes both in memory and on disk which allows executing distributed SQL
queries across different memory layers achieving the performance and scale of in-memory computing
together with the disk durability and strong consistency in one system. If the persistence is disabled
- Ignite can act as a pure <a href="/use-cases/database/in-memory-database.html" target="_blank">
+ Ignite can act as a pure <a href="/use-cases/database/in-memory-database.html">
in-memory database</a>.
</p>
</div>