[TYPO3-dam-devel] RFC #12525: Adding metadata or category to a file duplicates the file in table tx_dam [DBAL]

[Peter Kühn [wmdb]]

Hi Xavier,

I´m no databaseguru at all - so maybe this is a stupid question:

I know that MySQL 5.1 will be able to handle varchar(4000) but: is this true for 5.0 as well?
I think we have to keep in mind, that the majority of all installations is run on MySql and the majority of those on 5.0...

gRTz
pekue

> -----Ursprüngliche Nachricht-----
> Von: typo3-team-dam-bounces at lists.typo3.org [mailto:typo3-team-dam-
> bounces at lists.typo3.org] Im Auftrag von Xavier Perseguers
> Gesendet: Freitag, 9. Juli 2010 13:10
> An: typo3-team-dam at lists.typo3.org
> Betreff: [TYPO3-dam-devel] RFC #12525: Adding metadata or category to a
> file duplicates the file in table tx_dam [DBAL]
> 
> Hi,
> 
> This is an SVN patch request.
> 
> Type: Bugfix when using DBAL
> 
> Bugtracker reference:
> http://bugs.typo3.org/view.php?id=12525
> 
> Problem:
> After indexing a file, trying to add metadata or a category duplicates
> the file before adding information to a copy of the original record in
> table tx_dam.
> 
> DBAL Debug shows errors for typo3conf/ext/dam/mod_file/index.php:
> 
> ORA-00932: inconsistent datatypes: expected - got CLOB
> 
> Problem is related to file_path of table tx_dam that is defined as
> "text". This leads to queries such as
> 
> WHERE ... AND file_path = '/path/to/file'
> 
> which is invalid as the text column has been mapped as a CLOB in
> Oracle.
> Using varchar(4000) which is the limit of number of characters for a
> variable-length string column in Oracle solves the problem as the
> column is then mapped to VARCHAR2(4000)
> 
> Regards
> 
> Xavier Perseguers