ever needed a "case insensitive" content repository ?
it might be your case if you have to deal with ppl developing content on windows and mixing upper case filenames with lowercase links pointing to them or vice versa.
to workaround this i changed the "=" condition to "ilike", avail only to postgres v. 8 i think, in the content_item__get_id sql function where following comparaison is made
and
name = item_name;
