md5check adds a column in system table during install ( named md5checksum and varchar (64 ) ).
1) statements use to ALTER TABLE doesn't work with postgresql ( there shouldn't be any quotes around the columnname )
2) the sql statements used doesn't work with postgresql ( there must be single quotes used, not double ones in WHERE )
3) there are some warnings created by the md5check-rglob() function during usage. i wrote a somewhat different.
seems to me, that the last "foreach ( $paths as $p )" should catched by a if ($paths ) { .... }. Looks like at least my system returns false instead a empty array.
4) don't understand why not using a char(32) column. As long md5 is hard-coded in the module the result must be 32 byte fixed length in each case.
BTW: i've up and running modified code, but still testing. At this time i only want to publish, that module seems incompatible with postgres.
However people can ask by mail.
Comments
Comment #1
Pedja Grujić commentedIf you want to provide a patch we will gladly add it to 6.x release and use it for 7.x release
Comment #2
Pedja Grujić commented