[TYPO3-paymentlib] compatibility bread due to renaming of table fields
Franz Holzinger
franz at fholzinger.com
Wed Jul 4 13:27:49 CEST 2007
Hello Tonni,
with your change on Feb 28, 2007 you have renamed
extkey varchar(100) DEFAULT '' NOT NULL,
into
ext_key varchar(100) DEFAULT '' NOT NULL,
This is a serious _break in the compatibility_. Nobody can simply update
to the next higher version. I have to rewrite each Payment Library
extension only because of this change. And all extensions will the only
work with Payment Library 0.2.1 and not any more with 0.1.0
Is there any reason for renaming of this table field?
Greets,
Franz
More information about the TYPO3-project-paymentlib
mailing list