Skip to content

Releases: twisted/axiom

Axiom 0.9.0 release

26 Aug 12:31
0.9.0
8ad9385
Compare
Choose a tag to compare

Major:

  • (#107) Passwords are now stored hashed; make use of the APIs introduced in
    0.8.0 to set or change passwords.

Minor:

  • (#115) Axiom's internal schema now quotes all names to avoid collisions with
    future SQLite reserved words.

Axiom 0.8.0 release

03 Feb 08:33
8294eac
Compare
Choose a tag to compare

Major:

  • (#87) Axiom now creates tables with an explicit INTEGER PRIMARY KEY
    column, which means that VACUUM will no longer corrupt the database.
    axiomatic upgrade will migrate the existing tables in a store; as every
    table must be copied, this may take a while on large stores.
  • (#91) axiom.userbase.LoginAccount now has setPassword and
    replacePassword methods. In a future version plaintext passwords will no
    longer be stored at all, so applications must be migrated away from direct
    LoginAccount.password use.
  • (#89) axiom.store.Store takes a new parameter journalMode, and
    axiomatic a corresponding --journal-mode argument. The SQLite journal
    mode will be set to this value when the store is opened, and substores will
    inherit the setting. The current default is None which sets no mode at
    all, but this will change to u'WAL' in a future version.

Minor:

  • (#69) The exception raised when a store's persisted schema does not match the
    in-memory schema now shows the differences.
  • (#68) ORDER BY is now suppressed for deleteFromStore with no LIMIT.
  • (#88) There is a new @empowerment decorator for bestowing
    powerupInterfaces on an Item.

Axiom 0.8.0rc2 release

01 Feb 11:22
8294eac
Compare
Choose a tag to compare
Pre-release

Fix release artifacts.

Axiom 0.8.0rc1 release

28 Jan 16:12
caead00
Compare
Choose a tag to compare
Pre-release

Major:

  • (#87) Axiom now creates tables with an explicit INTEGER PRIMARY KEY
    column, which means that VACUUM will no longer corrupt the database.
    axiomatic upgrade will migrate the existing tables in a store; as every
    table must be copied, this may take a while on large stores.
  • (#91) axiom.userbase.LoginAccount now has setPassword and
    replacePassword methods. In a future version plaintext passwords will no
    longer be stored at all, so applications must be migrated away from direct
    LoginAccount.password use.
  • (#89) axiom.store.Store takes a new parameter journalMode, and
    axiomatic a corresponding --journal-mode argument. The SQLite journal
    mode will be set to this value when the store is opened, and substores will
    inherit the setting. The current default is None which sets no mode at
    all, but this will change to u'WAL' in a future version.

Minor:

  • (#69) The exception raised when a store's persisted schema does not match the
    in-memory schema now shows the differences.
  • (#68) ORDER BY is now suppressed for deleteFromStore with no LIMIT.
  • (#88) There is a new @Empowerment decorator for bestowing
    powerupInterfaces on an Item.

Axiom 0.8.0a1 pre-release

28 Jan 10:10
635d6ec
Compare
Choose a tag to compare
Pre-release

Testing actions.

Axiom 0.7.5 release

04 Feb 07:06
0.7.5
Compare
Choose a tag to compare

Major

  • Python 2.6 is now unsupported, due to Twisted dropping 2.6 support.
  • Fix an issue where the value of a reference pointing at a legacy item (ie.
    created in an upgrader) could be lost once the upgrade completed in some
    circumstances.
  • All attributes.bytes comparisons based on the LIKE SQL operator (like,
    notLike, startswith, and endswith) are deprecated. If SQLite was
    compiled with the SQLITE_LIKE_DOESNT_MATCH_BLOBS option (such as the
    Debian package does from version 3.10.0-1), these comparisons are always
    false; and even when this option is not active, the behaviour of the LIKE
    operator with BLOB values is unexpected (the operands are cast to TEXT
    before the comparison is done).

Minor

  • axiomatic start needs to handle some twistd arguments specially;
    fix an issue where arguments in the --arg=value form were not detected
    correctly (the -a value and --arg value forms were always detected
    correctly, so you can use these with older versions, if necessary).