-- Feature request: for the table 'related_samples' and similar tables
   that have two references to the same table, we need to tell
   the composite form generator to represent it table only once.

-- !! insertions of duplicated unique keys are not reported as erros
      as of current ^/trunk; checked good revision is 'svn up -r673'.

-- !! Usability bug: there is no longer way to add lithology_img
      images! The problem is that the 'natural_sample' is merged with
      the 'sample' in the edit form, but the related tables to be
      added are only shown for the 'sample' table, and there is no way
      to navigate to the 'natural_sample'...

-- I mark the previous bugs as solved (++), the solution being the fix
   in the `description` metadata table. We should think, however, how
   to make the system more servicable in the future.

-- Minor UI blooper: table 'samples' has column 'origin', however, drop
   down menu for search contains 'origin_id' for this column. It is not
   trivial to understand that user wanting to list all entries from
   New Caledonia is not able to do so by querying for
   'origin_id=New+Caledonia'.

-- Upon changing entry's external key ('extkey') REQUEST_URI stays the
   same, and the user might arrive at an empty page if the REQUEST_URI
   points at the now-non-existing record. Such situations have to be
   detected and resolved using for example UUIDs.

-- 1:1 related tables should not be mentioned in the 'experiment...'
   drop-down list, only 1:N tables.

-+ History tables should be ignored (when described with
   'visualisation="none"'). (Partial ad-hoc fix in
   ^/branches/saulius-searching).

++ Totally strange table editing form for images with 'format',
   'cssclass', etc. -- Reason: does not check 'fk' column type, just
   the presence of non-null fk_target. Should check also column type.

-- ID suggestion code is confused when non-numeric prefixes overlap
   for different ranges, e.g. 'VU-0000-0001' and VU-SZ00-0001'.

-- Suggesion of the PublicID (SolsaID) does not work for a new user
   that has no records yet recorded in a database.

   The reason why this is happening is that the new users lached
   SELECT privilege on the restful.* tables. Need to think how to
   change this behaviour, otherwise we get to the sutuation when
   suggestions of the IDs on the Web do not work for no obvious
   reason.

-- Creation of the new record works incorrectly if the table (and engine?) is
   specified in a query string, and not in the request URI.

-- Request for 'database/sample/' should be served identically as
   'database/sample' (unless we assign special meaning for 'sample/'?).

-- Unexpected behaviour upon 'search within':

   [Mon Apr 23 10:51:02.270089 2018] [cgi:error] [pid 23151:tid 140175258617600] [client 172.17.170.148:48994] AH01215: /home/saulius/public_html/restful/website/cgi-bin/db.pl: WARNING, incorrect filter expression '((year >= 2010) AND (title LIKE "Bragg")) AND (title LIKE "%")':: /home/saulius/public_html/restful/website/cgi-bin/db.pl, referer: https://perly-gate.ibt.lt/~saulius/restful/website/iucr.sqlite3/biblio?filter=%28year+%3E%3D+2010%29+AND+%28title+LIKE+%22Bragg%22%29&offset=0&order=year%3Ad%2Cjournal%3Aa%2Cvolume%3Aa%2Cissue%3Aa%2Cfirstpage%3Aa&rows=100&select_column=title&select_not_operator=&select_operator=like&search_value=%25&select_combining=within&.cgifields=select_combining
