[Checkins] SVN: relstorage/trunk/ Moved old changelog entries to HISTORY.txt.

Shane Hathaway shane at hathawaymix.org
Mon Oct 12 12:25:01 EDT 2009


Log message for revision 105026:
  Moved old changelog entries to HISTORY.txt.
  
  Removed README_ptBR.txt because it's too far out of date.
  
  Added doc about the cache-prefix option.
  

Changed:
  U   relstorage/trunk/CHANGES.txt
  A   relstorage/trunk/HISTORY.txt
  U   relstorage/trunk/README.txt
  D   relstorage/trunk/README_ptBR.txt

-=-
Modified: relstorage/trunk/CHANGES.txt
===================================================================
--- relstorage/trunk/CHANGES.txt	2009-10-12 14:49:55 UTC (rev 105025)
+++ relstorage/trunk/CHANGES.txt	2009-10-12 16:25:01 UTC (rev 105026)
@@ -85,283 +85,3 @@
 
 - Fixed minor test failures under Windows. Windows is now a supportable
   platform.
-
-
-1.1.3 (2009-02-04)
-------------------
-
-- In rare circumstances, ZODB can legitimately commit an object twice in a
-  single transaction.  Fixed RelStorage to accept that.
-
-- Auto reconnect to Oracle sometimes did not work because cx_Oracle was
-  raising a different kind of exception than expected.  Fixed.
-
-- Included LICENSE.txt in the source distribution.
-
-
-1.1.2 (2009-01-27)
-------------------
-
-- When both cache-servers and poll-interval are set, we now poll the
-  cache for changes on every request.  This makes it possible to use
-  a high poll-interval to reduce the database polling burden, yet
-  every client can see changes immediately.
-
-- Added the pack-dry-run option, which causes pack operations to only
-  populate the pack tables with the list of objects and states to pack,
-  but not actually pack.
-
-- Refined the pack algorithm.  It was not removing as many object states
-  as it should have.  As a bonus, there is now a method of adapters called
-  fill_object_refs(), which could be useful for debugging.  It ensures the
-  object_ref table is fully populated.
-
-- Began using zc.buildout for development.
-
-- Increased automated test coverage.
-
-- Fixed KeyError reporting to not trip over a related KeyError while logging.
-
-
-1.1.1 (2008-12-27)
-------------------
-
-- Worked around MySQL performance bugs in packing.  Used temporary
-  tables and another column in the pack_object table.  The
-  other databases may benefit from the optimization as well.
-
-- Applied an optimization using setinputsizes() to the Oracle code,
-  bringing write speed back up to where it was in version 1.0.
-
-
-1.1 (2008-12-19)
-----------------
-
-- Normalized poll-invalidation patches as Solaris' patch command would not
-  accept the current format. The patches now apply with:
-  patch -d lib/python/ZODB -p0 < poll-invalidation-1-zodb-3-X-X.patch
-
-- In MySQL, Use DROP TABLE IF EXISTS instead of TRUNCATE to clear 'temp_store'
-  because:
-
-  - TRUNCATE has one page of caveats in the MySQL documentation.
-  - TEMPORARY TABLEs have half a page of caveats when it comes to
-    replication.
-  - The end result is that 'temp_store' may not exist on the
-    replication slave at the exact same time(s) it exists on the
-    master.
-
-- Implemented the database size query in MySQL, based on a patch from
-  Kazuhiko Shiozaki.  Thanks!
-
-- Optimized Oracle object retrieval by causing BLOBs to be sent inline
-  when possible, based on a patch by Helge Tesdal.  By default, the
-  optimization is activated automatically when cx_Oracle 5 is used.
-
-- Updated the storage iterator code to be compatible with ZODB 3.9.
-  The RelStorage tests now pass with the shane-poll-invalidations branch
-  of ZODB 3.9.
-
-- Added a translation of README.txt to Brazilian Portuguese by
-  Rogerio Ferreira.  Thanks!
-
-
-1.1c1
------
-
-- Added optional memcache integration.  This is useful when the connection
-  to the relational database has high latency.
-
-- Made it possible to set the pack and memcache options in zope.conf.
-
-- Log more info when a KeyError occurs within RelStorage.
-
-
-1.1b2
------
-
-- Made the MySQL locks database-specific rather than server-wide.  This is
-  important for multi-database configurations.
-
-- In the PostgreSQL adapter, made the pack lock fall back to table locking
-  rather than advisory locks for PostgreSQL 8.1.
-
-- Changed a query for following object references (used during packing)
-  to work around a MySQL performance bug.  Thanks to Anton Stonor for
-  discovering this.
-
-
-1.1b1
------
-
-- Fixed the use of setup.py without setuptools.  Thanks to Chris Withers.
-
-- Fixed type coercion of the transaction extension field.  This fixes
-  an issue with converting databases.  Thanks to Kevin Smith for
-  discovering this.
-
-- Added logging to the pack code to help diagnose performance issues.
-
-- Additions to the object_ref table are now periodically committed
-  during pre_pack so that the work is not lost if pre_pack fails.
-
-- Modified the pack code to pack one transaction at a time and
-  release the commit lock frequently.  This should help large pack
-  operations.
-
-- Fixed buildout-based installation of the zodbconvert script.  Thanks to
-  Jim Fulton.
-
-
-1.0.1
------
-
-- The speedtest script failed if run on a test database that has no tables.
-  Now the script creates the tables if needed.  Thanks to Flavio Coelho
-  for discovering this.
-
-- Reworked the auto-reconnect logic so that applications never see
-  temporary database disconnects if possible.  Thanks to Rigel Di Scala
-  for pointing out this issue.
-
-- Improved the log messages explaining database connection failures.
-
-- Moved poll_invalidations to the common adapter base class, reducing the
-  amount of code to maintain.
-
-
-1.0
----
-
-- Added a utility for converting between storages called zodbconvert.
-
-
-1.0c1
------
-
-- The previous fix for non-ASCII characters was incorrect.  Now transaction
-  metadata is stored as raw bytes.  A schema migration is required; see
-  notes/migrate-1.0-beta.txt.
-
-- Integrated setuptools and made an egg.
-
-
-1.0 beta
---------
-
-- Renamed to reflect expanding database support.
-
-- Added support for Oracle 10g.
-
-- Major overhaul with many scalability and reliability improvements,
-  particularly in the area of packing.
-
-- Moved to svn.zope.org and switched to ZPL 2.1.
-
-- Made two-phase commit optional in both Oracle and PostgreSQL.  They
-  both use commit_lock in such a way that the commit is not likely to
-  fail in the second phase.
-
-- Switched most database transaction isolation levels from serializable
-  to read committed.  It turns out that commit_lock already provides
-  the serializability guarantees we need, so it is safe to take advantage
-  of the potential speed gains.  The one major exception is the load
-  connection, which requires an unchanging view of the database.
-
-- Stored objects are now buffered in a database table rather than a file.
-
-- Stopped using the LISTEN and NOTIFY statements in PostgreSQL since
-  they are not strictly transactional in the sense we require.
-
-- Started using a prepared statement in PostgreSQL for getting the
-  newest transaction ID quickly.
-
-- Removed the code in the Oracle adapter for retrying connection attempts.
-  (It is better to just reconfigure Oracle.)
-
-- Added support for MySQL 5.0.
-
-- Added the poll_interval option.  It reduces the frequency of database
-  polls, but it also increases the potential for conflict errors on
-  servers with high write volume.
-
-- Implemented the storage iterator protocol, making it possible to copy
-  transactions to and from FileStorage and other RelStorage instances.
-
-- Fixed a bug that caused OIDs to be reused after importing transactions.
-  Added a corresponding test.
-
-- Made it possible to disable garbage collection during packing.
-  Exposed the option in zope.conf.
-
-- Valery Suhomlinov discovered a problem with non-ASCII data in transaction
-  metadata.  The problem has been fixed for all supported databases.
-
-
-PGStorage history
-=================
-
-0.4
----
-
-- Began using the PostgreSQL LISTEN and NOTIFY statements as a shortcut
-  for invalidation polling.
-
-- Removed the commit_order code.  The commit_order idea was intended to
-  allow concurrent commits, but that idea is a little too ambitious while
-  other more important ideas are being tested.  Something like it may
-  come later.
-
-- Improved connection management: only one database connection is
-  held continuously open per storage instance.
-
-- Reconnect to the database automatically.
-
-- Removed test mode.
-
-- Switched from using a ZODB.Connection subclass to a ZODB patch.  The
-  Connection class changes in subtle ways too often to subclass reliably;
-  a patch is much safer.
-
-- PostgreSQL 8.1 is now a dependency because PGStorage uses two phase commit.
-
-- Fixed an undo bug.  Symptom: attempting to examine the undo log revealed
-  broken pickles.  Cause: the extension field was not being wrapped in
-  psycopg2.Binary upon insert.  Solution: used psycopg2.Binary.
-  Unfortunately, this doesn't fix existing transactions people have
-  committed.  If anyone has any data to keep, fixing the old transactions
-  should be easy.
-
-- Moved from a private CVS repository to Sourceforge.
-  See http://pgstorage.sourceforge.net .  Also switched to the MIT license.
-
-- David Pratt added a basic getSize() implementation so that the Zope
-  management interface displays an estimate of the size of the database.
-
-- Turned PGStorage into a top-level package.  Python generally makes
-  top-level packages easier to install.
-
-
-0.3
----
-
-- Made compatible with Zope 3, although an undo bug apparently remains.
-
-
-0.2
----
-
-- Fixed concurrent commits, which were generating deadlocks.  Fixed by
-  adding a special table, "commit_lock", which is used for
-  synchronizing increments of commit_seq (but only at final commit.)
-  If you are upgrading from version 0.1, you need to change your
-  database using the 'psql' prompt:
-
-    create table commit_lock ();
-
-- Added speed tests and an OpenDocument spreadsheet comparing
-  FileStorage / ZEO with PGStorage.  PGStorage wins at reading objects
-  and writing a lot of small transactions, while FileStorage / ZEO
-  wins at writing big transactions.  Interestingly, they tie when
-  writing a RAM disk.
-

Copied: relstorage/trunk/HISTORY.txt (from rev 104978, relstorage/trunk/CHANGES.txt)
===================================================================
--- relstorage/trunk/HISTORY.txt	                        (rev 0)
+++ relstorage/trunk/HISTORY.txt	2009-10-12 16:25:01 UTC (rev 105026)
@@ -0,0 +1,279 @@
+
+1.1.3 (2009-02-04)
+------------------
+
+- In rare circumstances, ZODB can legitimately commit an object twice in a
+  single transaction.  Fixed RelStorage to accept that.
+
+- Auto reconnect to Oracle sometimes did not work because cx_Oracle was
+  raising a different kind of exception than expected.  Fixed.
+
+- Included LICENSE.txt in the source distribution.
+
+
+1.1.2 (2009-01-27)
+------------------
+
+- When both cache-servers and poll-interval are set, we now poll the
+  cache for changes on every request.  This makes it possible to use
+  a high poll-interval to reduce the database polling burden, yet
+  every client can see changes immediately.
+
+- Added the pack-dry-run option, which causes pack operations to only
+  populate the pack tables with the list of objects and states to pack,
+  but not actually pack.
+
+- Refined the pack algorithm.  It was not removing as many object states
+  as it should have.  As a bonus, there is now a method of adapters called
+  fill_object_refs(), which could be useful for debugging.  It ensures the
+  object_ref table is fully populated.
+
+- Began using zc.buildout for development.
+
+- Increased automated test coverage.
+
+- Fixed KeyError reporting to not trip over a related KeyError while logging.
+
+
+1.1.1 (2008-12-27)
+------------------
+
+- Worked around MySQL performance bugs in packing.  Used temporary
+  tables and another column in the pack_object table.  The
+  other databases may benefit from the optimization as well.
+
+- Applied an optimization using setinputsizes() to the Oracle code,
+  bringing write speed back up to where it was in version 1.0.
+
+
+1.1 (2008-12-19)
+----------------
+
+- Normalized poll-invalidation patches as Solaris' patch command would not
+  accept the current format. The patches now apply with:
+  patch -d lib/python/ZODB -p0 < poll-invalidation-1-zodb-3-X-X.patch
+
+- In MySQL, Use DROP TABLE IF EXISTS instead of TRUNCATE to clear 'temp_store'
+  because:
+
+  - TRUNCATE has one page of caveats in the MySQL documentation.
+  - TEMPORARY TABLEs have half a page of caveats when it comes to
+    replication.
+  - The end result is that 'temp_store' may not exist on the
+    replication slave at the exact same time(s) it exists on the
+    master.
+
+- Implemented the database size query in MySQL, based on a patch from
+  Kazuhiko Shiozaki.  Thanks!
+
+- Optimized Oracle object retrieval by causing BLOBs to be sent inline
+  when possible, based on a patch by Helge Tesdal.  By default, the
+  optimization is activated automatically when cx_Oracle 5 is used.
+
+- Updated the storage iterator code to be compatible with ZODB 3.9.
+  The RelStorage tests now pass with the shane-poll-invalidations branch
+  of ZODB 3.9.
+
+- Added a translation of README.txt to Brazilian Portuguese by
+  Rogerio Ferreira.  Thanks!
+
+
+1.1c1
+-----
+
+- Added optional memcache integration.  This is useful when the connection
+  to the relational database has high latency.
+
+- Made it possible to set the pack and memcache options in zope.conf.
+
+- Log more info when a KeyError occurs within RelStorage.
+
+
+1.1b2
+-----
+
+- Made the MySQL locks database-specific rather than server-wide.  This is
+  important for multi-database configurations.
+
+- In the PostgreSQL adapter, made the pack lock fall back to table locking
+  rather than advisory locks for PostgreSQL 8.1.
+
+- Changed a query for following object references (used during packing)
+  to work around a MySQL performance bug.  Thanks to Anton Stonor for
+  discovering this.
+
+
+1.1b1
+-----
+
+- Fixed the use of setup.py without setuptools.  Thanks to Chris Withers.
+
+- Fixed type coercion of the transaction extension field.  This fixes
+  an issue with converting databases.  Thanks to Kevin Smith for
+  discovering this.
+
+- Added logging to the pack code to help diagnose performance issues.
+
+- Additions to the object_ref table are now periodically committed
+  during pre_pack so that the work is not lost if pre_pack fails.
+
+- Modified the pack code to pack one transaction at a time and
+  release the commit lock frequently.  This should help large pack
+  operations.
+
+- Fixed buildout-based installation of the zodbconvert script.  Thanks to
+  Jim Fulton.
+
+
+1.0.1
+-----
+
+- The speedtest script failed if run on a test database that has no tables.
+  Now the script creates the tables if needed.  Thanks to Flavio Coelho
+  for discovering this.
+
+- Reworked the auto-reconnect logic so that applications never see
+  temporary database disconnects if possible.  Thanks to Rigel Di Scala
+  for pointing out this issue.
+
+- Improved the log messages explaining database connection failures.
+
+- Moved poll_invalidations to the common adapter base class, reducing the
+  amount of code to maintain.
+
+
+1.0
+---
+
+- Added a utility for converting between storages called zodbconvert.
+
+
+1.0c1
+-----
+
+- The previous fix for non-ASCII characters was incorrect.  Now transaction
+  metadata is stored as raw bytes.  A schema migration is required; see
+  notes/migrate-1.0-beta.txt.
+
+- Integrated setuptools and made an egg.
+
+
+1.0 beta
+--------
+
+- Renamed to reflect expanding database support.
+
+- Added support for Oracle 10g.
+
+- Major overhaul with many scalability and reliability improvements,
+  particularly in the area of packing.
+
+- Moved to svn.zope.org and switched to ZPL 2.1.
+
+- Made two-phase commit optional in both Oracle and PostgreSQL.  They
+  both use commit_lock in such a way that the commit is not likely to
+  fail in the second phase.
+
+- Switched most database transaction isolation levels from serializable
+  to read committed.  It turns out that commit_lock already provides
+  the serializability guarantees we need, so it is safe to take advantage
+  of the potential speed gains.  The one major exception is the load
+  connection, which requires an unchanging view of the database.
+
+- Stored objects are now buffered in a database table rather than a file.
+
+- Stopped using the LISTEN and NOTIFY statements in PostgreSQL since
+  they are not strictly transactional in the sense we require.
+
+- Started using a prepared statement in PostgreSQL for getting the
+  newest transaction ID quickly.
+
+- Removed the code in the Oracle adapter for retrying connection attempts.
+  (It is better to just reconfigure Oracle.)
+
+- Added support for MySQL 5.0.
+
+- Added the poll_interval option.  It reduces the frequency of database
+  polls, but it also increases the potential for conflict errors on
+  servers with high write volume.
+
+- Implemented the storage iterator protocol, making it possible to copy
+  transactions to and from FileStorage and other RelStorage instances.
+
+- Fixed a bug that caused OIDs to be reused after importing transactions.
+  Added a corresponding test.
+
+- Made it possible to disable garbage collection during packing.
+  Exposed the option in zope.conf.
+
+- Valery Suhomlinov discovered a problem with non-ASCII data in transaction
+  metadata.  The problem has been fixed for all supported databases.
+
+
+PGStorage history
+=================
+
+0.4
+---
+
+- Began using the PostgreSQL LISTEN and NOTIFY statements as a shortcut
+  for invalidation polling.
+
+- Removed the commit_order code.  The commit_order idea was intended to
+  allow concurrent commits, but that idea is a little too ambitious while
+  other more important ideas are being tested.  Something like it may
+  come later.
+
+- Improved connection management: only one database connection is
+  held continuously open per storage instance.
+
+- Reconnect to the database automatically.
+
+- Removed test mode.
+
+- Switched from using a ZODB.Connection subclass to a ZODB patch.  The
+  Connection class changes in subtle ways too often to subclass reliably;
+  a patch is much safer.
+
+- PostgreSQL 8.1 is now a dependency because PGStorage uses two phase commit.
+
+- Fixed an undo bug.  Symptom: attempting to examine the undo log revealed
+  broken pickles.  Cause: the extension field was not being wrapped in
+  psycopg2.Binary upon insert.  Solution: used psycopg2.Binary.
+  Unfortunately, this doesn't fix existing transactions people have
+  committed.  If anyone has any data to keep, fixing the old transactions
+  should be easy.
+
+- Moved from a private CVS repository to Sourceforge.
+  See http://pgstorage.sourceforge.net .  Also switched to the MIT license.
+
+- David Pratt added a basic getSize() implementation so that the Zope
+  management interface displays an estimate of the size of the database.
+
+- Turned PGStorage into a top-level package.  Python generally makes
+  top-level packages easier to install.
+
+
+0.3
+---
+
+- Made compatible with Zope 3, although an undo bug apparently remains.
+
+
+0.2
+---
+
+- Fixed concurrent commits, which were generating deadlocks.  Fixed by
+  adding a special table, "commit_lock", which is used for
+  synchronizing increments of commit_seq (but only at final commit.)
+  If you are upgrading from version 0.1, you need to change your
+  database using the 'psql' prompt:
+
+    create table commit_lock ();
+
+- Added speed tests and an OpenDocument spreadsheet comparing
+  FileStorage / ZEO with PGStorage.  PGStorage wins at reading objects
+  and writing a lot of small transactions, while FileStorage / ZEO
+  wins at writing big transactions.  Interestingly, they tie when
+  writing a RAM disk.
+


Property changes on: relstorage/trunk/HISTORY.txt
___________________________________________________________________
Added: svn:mergeinfo
   + 

Modified: relstorage/trunk/README.txt
===================================================================
--- relstorage/trunk/README.txt	2009-10-12 14:49:55 UTC (rev 105025)
+++ relstorage/trunk/README.txt	2009-10-12 16:25:01 UTC (rev 105026)
@@ -382,6 +382,12 @@
         modules available through PyPI.  This setting has no effect unless
         cache-servers is set.
 
+``cache-prefix``
+        The prefix for all keys in the cache.  All clients using a
+        database should use the same cache-prefix.  Use this if you use
+        a single cache for multiple databases.
+
+
 Adapter Options
 ===============
 

Deleted: relstorage/trunk/README_ptBR.txt
===================================================================
--- relstorage/trunk/README_ptBR.txt	2009-10-12 14:49:55 UTC (rev 105025)
+++ relstorage/trunk/README_ptBR.txt	2009-10-12 16:25:01 UTC (rev 105026)
@@ -1,239 +0,0 @@
-
-
-Visão Geral
-===========
-
-  RelStorage é uma implementação de storage para o ZODB que provê armazenamento num
-banco de dados relacional.  PostgreSQL 8.1 e superior (via psycopg2), MySQL 5.0.x (via
-MySQLdb), e Oracle 10g (via cx_Oracle) são atualmente suportados.
-
-  RelStorage substitui o projeto PGStorage.
-
-  Consulte:
-
-     http://wiki.zope.org/ZODB/RelStorage         (wiki)
-     http://shane.willowrise.com/                 (blog)
-     http://pypi.python.org/pypi/RelStorage       (PyPI entry e downloads)
-
-
-Características
-===============
-
-  * É um substituto para o FileStorage e ZEO.
-  * Há um caminho simples para converter FileStorage para RelStorage e reverter novamente. 
-Você pode também converter uma instância de RelStorage para um diferente banco de dados relacional.
-  * Projetado para sites com grande volume: Múltiplas instâncias do ZODB podem compartilhar o mesmo
-banco de dados. Isto é similar para o ZEO, mas RelStorage não requer ZEO.
-  * De acordo com alguns testes, RelStorage manipula alta concorrência melhor que
-a combinação de ZEO e FileStorage.
-  * Enquanto que o FileStorage toma mais tempo para iniciar à medida que o banco de dados cresce, devido a uma
-indexação de todos os objetos na memória, RelStorage inicia rapidamente sem levar em consideração o
-tamanho do banco de dados.
-  * Suporta undo e packing.
-  * Livre, open source (ZPL 2.1)
-
-
-Instalação no Zope
-==================
-
-  Você pode instalar RelStorage usando easy_install::
-
-    easy_install RelStorage
-
-  Se você não está usando easy_install (parte do pacote setuptools), você pode
-conseguir a última release no PyPI (http://pypi.python.org/pypi/RelStorage), então
-instale o pacote relstorage no diretório lib/python de um ou outro
-SOFTWARE_HOME ou da INSTANCE_HOME.  Você pode fazer isso como o seguinte
-comando::
-
-    python2.4 setup.py install --install-lib=${INSTANCE_HOME}/lib/python
-
-  Antes de você poder usar o RelStorage, ZODB precisa ter o patch de invalidação de checagem
-aplicado. Obtenha-o no Subversion (http://svn.zope.org/relstorage/trunk/). 
-Há duas versões do patch: uma para ZODB 3.7.1 (que é parte do Zope
-2.10.5) e outra para ZODB 3.8.0 (que é parte do Zope 2.11).  O patch não tem
-efeito no ZODB exceto quando se está usando o RelStorage.  Esperamos, uma futura release de
-ZODB que irá incluir esta característica.
-
-  Você precisa de um adaptador de banco de dados para o Python que corresponda com seu banco de dados. 
-Instale psycopg2, MySQLdb 1.2.2+, ou cx_Oracle 4.3+.  Note que o Debian Etch
-disponibiliza MySQLdb 1.2.1, mas esta versão tem um bug na manipulação de BLOB que se manifesta
-somente com certas configurações de caracteres.  MySQLdb 1.2.2 corrige o
-bug.  Também, MySQL 5.1.23 tem bugs maiores que levam a perda de dados quando é feito o packing,
-assim MySQL 5.1 não é recomendado neste momento.
-
-  Finalmente, modifique o etc/zope.conf de sua instância de Zope.  Remova o ponto de montagem
-principal e adicione um dos seguintes blocos.  Para PostgreSQL::
-
-    %import relstorage
-    <zodb_db main>
-      mount-point /
-      <relstorage>
-        <postgresql>
-          # O dsn é opcional, assim como são cada parametro no dsn.
-          dsn dbname='zodb' user='username' host='localhost' password='pass'
-        </postgresql>
-      </relstorage>
-    </zodb_db>
-
-  Para MySQL::
-
-    %import relstorage
-    <zodb_db main>
-      mount-point /
-      <relstorage>
-        <mysql>
-          # A maioria das opções providas pelo MySQLdb estão disponíveis.
-          # Consulte component.xml.
-          db zodb
-        </mysql>
-      </relstorage>
-    </zodb_db>
-
-  Para Oracle (10g XE neste exemplo)::
-
-    %import relstorage
-    <zodb_db main>
-      mount-point /
-      <relstorage>
-        <oracle>
-          user username
-          password pass
-          dsn XE
-        </oracle>
-     </relstorage>
-    </zodb_db>
-
-Migrando de FileStorage
-=======================
-
-  Você pode converter uma instância de FileStorage para RelStorage e reverter usando o utilitário
-chamado ZODBConvert.  Consulte http://wiki.zope.org/ZODB/ZODBConvert.
-
-
-Migrando de PGStorage
-=====================
-
-  O seguinte script migra sua base de dados de PGStorage para RelStorage 1.0
-beta:
-
-    migrate.sql_
-
-    .. _migrate.sql:
-http://svn.zope.org/*checkout*/relstorage/trunk/notes/migrate.sql
-
-  Após fazer isto, você ainda precisa migrar da versão 1.0 beta para a última
-release.
-
-
-Migrando para uma nova versão do RelStorage
-===========================================
-
-  Às vezes o RelStorage necessita de uma modificação de schema junto com uma atualização
-do software.  Esperamos, que isto não seja frequentemente necessário.
-
-  Para migrar da versão 1.0 beta para a versão 1.0c1, consulte:
-
-    migrate-1.0-beta.txt_
-
-    .. _migrate-1.0-beta.txt:
-http://svn.zope.org/*checkout*/relstorage/trunk/notes/migrate-1.0-beta.txt
-
-  Para migrar da versão 1.0.1 para a versão 1.1b1, consulte:
-
-    migrate-1.0.1.txt_
-
-    .. _migrate-1.0.1.txt:
-http://svn.zope.org/*checkout*/relstorage/branches/1.1/notes/migrate-1.0.1.txt
-
-
-Atributos Opcionais
-===================
-
-  poll-interval
-
-    Esta opção é proveitosa se você necessita reduzir o tráfego do banco de dados.  Se configurada,
-o RelStorage irá checar mudanças no banco de dados com menos frequência.  Um ajuste de 1 a 5
-segundos deverá ser suficiente para a maioria dos sistemas.  Fração de segundos são permitidos.
-
-    Enquanto este ajuste poderia não afetar a integridade do banco de dados, ele aumenta a
-probabilidade de transações baseadas em dados antigos, levando a conflitos.  Dessa forma um
-ajuste diferente de zero pode danificar a perfomance de servidores com alto volume de escrita.
-
-    Para habilitar este atributo, adicione uma linha similar a "poll-interval 2" dentro de
-uma secão <relstorage> do zope.conf.
-
-  pack-gc
-
-    Se pack-gc for falsa, operações de pack não efetuarão a coleta de lixo. 
-A coleta de lixo é habilitada por padrão.
-
-    Se o coletor de lixo estiver desabilitado, operações de pack manterão uma de suas menores
-revisões de cada objeto.  Com a coleta de lixo desabilitada, o código de pack não
-necessita seguir referências de objetos, fazendo packing de modo muito mais rápido. 
-No entanto, alguns dos benefícios podem ser perdidos devido a sempre aumentar o número de 
-objetos não usados.
-
-    Desabilitando a coleta de lixo é também cortada a segurança que referências inter-database 
-nunca quebrem.
-
-    Para desabilitar a coleta de lixo, adicione a linha "pack-gc no" dentro de uma
-seção <relstorage> do zope.conf.
-
-
-Desenvolvimento
-===============
-
-  Você pode fazer o checkout do Subversion usando o seguinte comando::
-
-    svn co svn://svn.zope.org/repos/main/relstorage/trunk RelStorage
-
-  Você pode também ver o código:
-
-    http://svn.zope.org/relstorage/trunk/
-
-  O melhor lugar para discutir sobre o desenvolvimento do RelStorage é a lista zodb-dev.
-
-
-
-FAQ
-===
-
-  P: Como eu posso ajudar?
-
-    R: A melhor caminho de ajudar é testar e prover informações de um banco de dados
-específico.  Fazer perguntas sobre RelStorage na lista zodb-dev.
-
-  P: Posso efetuar consultas SQL nos dados no banco de dados?
-
-    R: Não.  Semelhante ao FileStorage e DirectoryStorage, RelStorage armazena os dados
-como conserva, tornando difícil para qualquer coisa com exceção do ZODB interpretar os dados.  Um
-projeto anterior chamado Ape tentou armazenar dados em um verdadeiro caminho relacional,
-mas aconteceu que o Ape trabalhou muito mais contra os princípios do ZODB e
-conseqüentemente não pode ser confiável o bastante para uso em produção.  RelStorage, em
-outra mão, é muito mais perto para um usual ZODB storage, e é então
-muito seguro para uso em produção.
-
-  P: De que forma é comparado o desempenho do RelStorage com FileStorage?
-
-    R: De acordo com benchmarks, RelStorage com PostgreSQL é frequentemente mais rápido que
-o FileStorage, especialmente sobre alta concorrência.
-
-  P: Porque eu deveria escolher o RelStorage?
-
-    R: Porque o RelStorage é uma pequena camada que constrói corretamente em bancos de dados
-de classe mundial.  Estes bancos de dados tem comprovado confiabilidade e escalabilidade, junto com
-numerosas opções de suporte.
-
-  P: O RelStorage pode substituir o ZRS (Zope Replication Services)?
-
-    R: Em teoria, sim.  Com o RelStorage, você pode usar as características de replicação
-nativa para seu banco de dados.  No entanto, esta capacidade não foi testada ainda.
-
-
-Tradução para o Português do Brasil
-===================================
-
-Rogerio Ferreira
-Site: http://rogerioferreira.objectis.net
-Email: rogerio at 4linux.com.br
\ No newline at end of file



More information about the checkins mailing list