Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

TODO.html

Blame
    • Bruce Momjian's avatar
      9f6ed2f4
      Update wording: · 9f6ed2f4
      Bruce Momjian authored
      <   Currently, ALTER USER and ALTER DATABASE support per-user and
      >   Currently ALTER USER and ALTER DATABASE support per-user and
      < 	  Currently, subtracting one date from another that crosses a
      > 	  Currently subtracting one date from another that crosses a
      <   Currently, SQL-language functions can only refer to parameters via $1, etc
      >   Currently SQL-language functions can only refer to dollar parameters,
      >   e.g. $1
      <   Currently, queries prepared via the libpq API are planned on first
      >   Currently queries prepared via the libpq API are planned on first
      < 	  Currently, SET <tab> causes a database lookup to check all
      > 	  Currently SET <tab> causes a database lookup to check all
      < 	  Currently, all statement results are transferred to the libpq
      > 	  Currently all statement results are transferred to the libpq
      9f6ed2f4
      History
      Update wording:
      Bruce Momjian authored
      <   Currently, ALTER USER and ALTER DATABASE support per-user and
      >   Currently ALTER USER and ALTER DATABASE support per-user and
      < 	  Currently, subtracting one date from another that crosses a
      > 	  Currently subtracting one date from another that crosses a
      <   Currently, SQL-language functions can only refer to parameters via $1, etc
      >   Currently SQL-language functions can only refer to dollar parameters,
      >   e.g. $1
      <   Currently, queries prepared via the libpq API are planned on first
      >   Currently queries prepared via the libpq API are planned on first
      < 	  Currently, SET <tab> causes a database lookup to check all
      > 	  Currently SET <tab> causes a database lookup to check all
      < 	  Currently, all statement results are transferred to the libpq
      > 	  Currently all statement results are transferred to the libpq