Hi,
I don't know if this is supported against postgresql, but in recent revisions comparisons between varchar and int requires an explicit cast, which breaks this module.
What I've seen is "SELECT count(g2_mapMap.g_itemId) FROM g2_mapMap WHERE g2_mapMap.g_itemId IN (25,29,34)" which returns an error from the database : "ERROR: IN types character varying and integer cannot be matched". This happens when attempting to access the gallery home page.
Apparently, this can be fixed by casting the query explicitly, i.e.
"SELECT count(g2_mapMap.g_itemId) FROM g2_mapMap WHERE g2_mapMap.g_itemId::INT IN (25,29,34)", which worked as a query. Unfortunately I have no idea where in the code this would need patched, and what else needs looking at if postgresql is indeed a viable target.
I guess altering the schema would also fix this, but I don't know the code and have no idea how this would affect it!
Anyway, hope this helps,
Eamonn
This is probably fixed in SVN for new installs. To fix your particular case, you might be able to modify the schema stored in the database to make it work. You could try the following database commands (assumes your table prefix is g2_ and your column prefix is g_):
UPDATE g2_Schema SET g_createSql='CREATE TABLE DB_TABLE_PREFIXmapMap(\n DB_COLUMN_PREFIXitemId varchar(11) NOT NULL,\n DB_COLUMN_PREFIXfield varchar(128) NOT NULL,\n DB_COLUMN_PREFIXvalue varchar(255),\n DB_COLUMN_PREFIXsetId int(11),\n DB_COLUMN_PREFIXsetType int(11),\n INDEX DB_TABLE_PREFIXmapMap_75985(DB_COLUMN_PREFIXitemId)\n) TYPE=DB_TABLE_TYPE ;\n\nINSERT INTO DB_TABLE_PREFIXSchema (\n DB_COLUMN_PREFIXname,\n DB_COLUMN_PREFIXmajor,\n DB_COLUMN_PREFIXminor\n) VALUES('mapMap', 1, 1);\n\n', g_info='a:1:{s:6:"mapMap";a:5:{s:6:"itemId";a:3:{s:4:"type";i:2;s:4:"size";i:2;s:7:"notNull";b:1;}s:5:"field";a:3:{s:4:"type";i:2;s:4:"size";i:2;s:7:"notNull";b:1;}s:5:"value";a:2:{s:4:"type";i:2;s:4:"size";i:4;}s:5:"setId";a:2:{s:4:"type";i:1;s:4:"size";i:2;}s:7:"setType";a:2:{s:4:"type";i:1;s:4:"size";i:2;}}}' WHERE g_name='mapMap'
I don't know pgsql syntax at all, so I don't know if that command will work as I've written it. The important part is the g_info field, so do whatever you have to do to get that into your database (only for the row with g_name='mapMap'!). That string tells Gallery the format of the fields for storing data for the Google Map module. Previously the itemId column was set as an integer but the schema was not changed accordingly when the column was changed to a string.