Skip to content
Snippets Groups Projects
  1. Nov 26, 2007
  2. Nov 25, 2007
  3. Oct 16, 2007
  4. Aug 29, 2007
  5. Aug 16, 2007
  6. Jun 06, 2007
    • Fons Rademakers's avatar
      From Olivier: · 6686d963
      Fons Rademakers authored
      import the FTGL package provided by Henry Maddocks to allow TTF font
      display in OpenGL.
      
      
      git-svn-id: http://root.cern.ch/svn/root/trunk@18965 27541ba8-7e3a-0410-8455-c3a389f83636
      6686d963
    • Fons Rademakers's avatar
      From Dennis Box: · 548e771c
      Fons Rademakers authored
      A Postgres implementation of TSQLStatement.
      The purpose and intent of TSQLStatement is documented at
      
      http://root.cern.ch/root/html/TSQLStatement.html
      
      The following commentary corresponds item by item to the above url:
      
      1) Creation of statement
      Prepared statements were not explicitly
      supported in PostGreSQL API libpq until server version 8.2.3
      released 12/2006.
      
      This implementation checks if prepared statements are supported
      at compile time and 'stubs' out TPgSQLStatement if necessary.
      
      2) Insert data into data base
      
      MySQL and ODBC both use the following idiom for insert placeholders:
      
        TSQLStatement* stmt = serv->Statement("INSERT INTO TESTTABLE (ID1,\
            ID2, FFIELD ) VALUES (?, ?, ? )", 100);
      
      Unfortunately for code portability, Oracle implements the same statement
      like so:
      
        TSQLStatement* stmt = serv->Statement("INSERT INTO TESTTABLE (ID1,\
            ID2, FFIELD ) VALUES (:1,:2,:3 )", 100);
      
      Even more unfortunately, postgres chose to do it this way:
      
        TSQLStatement* stmt = serv->Statement("INSERT INTO TESTTABLE (ID1,\
            ID2, FFIELD ) VALUES ($1, $2, $3 )", 100);
      
      3) Getting data from database
      Libpq API supports sending/retrieving data as choice of string types or
      native types from server. Unfortunately, some native types are poorly
      documented, for example date and time native representation varies depending
      on compiler options given when server was built. Dates can be
      either 64 bit ints or double precision floating point, representing
      (+/-)microseconds since epoch (which was chosen to be 2001-01-01 00:00:01)
      
      Native format values come as big-endian values meaning they need to
      be swapped on linux but not on solaris, and the various time
      manipulation functions the server uses are not exposed in the libpq
      API.
      
      I elected to use the 'string' format for this first implementation, if
      the API changes to make dealing with dates and times in native format
      more palatable I may re-write this class in hopes of making it faster.
      
      4. Working with date/time parameters
      Fully supported, see item 3
      
      5. Binary data
      Fully supported, see attached test program.  Note that postgres calls
      these columns 'bytea'  type instead of 'blob' type.
      
      
      git-svn-id: http://root.cern.ch/svn/root/trunk@18959 27541ba8-7e3a-0410-8455-c3a389f83636
      548e771c
  7. May 29, 2007
  8. May 16, 2007
  9. May 03, 2007
  10. Apr 25, 2007
  11. Mar 19, 2007
  12. Mar 16, 2007
  13. Jan 10, 2007
  14. Dec 02, 2006
  15. Dec 01, 2006
  16. Nov 17, 2006
  17. Oct 20, 2006
  18. Oct 09, 2006
  19. Sep 22, 2006
  20. Sep 20, 2006
  21. Aug 24, 2006
  22. Aug 18, 2006
  23. Jul 11, 2006
  24. Jul 10, 2006
  25. May 26, 2006
  26. Apr 18, 2006
  27. Mar 21, 2006
  28. Jan 09, 2006
  29. Dec 15, 2005
  30. Dec 14, 2005
  31. Dec 11, 2005
  32. Dec 09, 2005
Loading