==============================
Known Problems in Gnatcoll 1.7
==============================

Copyright (C) 2013-2015, AdaCore

KP-17-O203-001 Postgresql: Insert_and_Get_PK fails with string prepared query

  Problem:    When you use a Prepared_Statement for a query given as a string,
              and use that in a Insert_and_Get_PK call, Gnatcoll generates an
              invalid query and postgreSQL complains.

  Status:     Fixed in Gnatcoll 1.8.0 on 2015-02-04

  Workaround: Send an INSERT statement ending with " RETURNING id" via
              Execute, and use the Last_Id function to get the actual id.

KP-17-O130-001 Postgresql: show full error message when connection fails

  Problem:    When the connection to the database fails, the specific
              message from the server (like "invalid port number") is not
              available to the application.

  Status:     Fixed in Gnatcoll 1.8.0. on 2015-01-30

  Workaround: Test the connection string (which is part of the error message)
              by using the command line client psql.

KP-17-O126-034 GNATCOLL.Projects.Other_File and separate units

  Problem:    The Other_File for a separate unit (say 'parent-child.adb')
              is returned incorrectly as 'parent-child.ads', whereas it
              should be 'parent.ads'.

  Status:     Fixed in Gnatcoll 1.8.0 on 2015-01-28

  Workaround: Use Info to get the name of the unit and get the file name
              for the parent unit.

KP-17-O114-020 GNATCOLL.JSON not quoting control characters

  Problem:    When adding a string that contains control characters (like
              ctrl-Z), the resulting JSON is not parsed correctly in some
              cases (for instance Firefox).

  Status:     Fixed in Gnatcoll 1.8.0 on 2015-01-19

  Workaround: Do a second pass on the string and escape such characters with
              GNATCOLL.JSON.Utility.Escape_Non_Print_Character.

KP-17-NB11-001 In_Transaction returns True without automatic transactions

  Problem:    If you disable automatic handling of transactions in
              GNATCOLL.SQL.Exec, the function In_Transaction always returns
              True.

  Status:     Fixed in Gnatcoll 1.8.0 on 2014-11-13

  Workaround: In this mode, GNATCOLL does not send BEGIN or COMMIT commands
              automatically, so your application can in fact keep track of
              whether it started a transaction explicitly.

KP-17-NA29-019 GNATCOLL.Projects.Info_Set does not set file information

  Problem:    Using Info_Set to retrieve information a source file (unit
              name, language,...) will not set the file name in the result.
              This differs from what GNATCOLL.Projects.Info does.

  Status:     Fixed in Gnatcoll 1.8.0 on 2014-11-06

  Workaround: The file was passed as a parameter to Info_Set, so it is in
              general available to the code.
