Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 25 3月, 2017 5 次提交
  3. 24 3月, 2017 9 次提交
  5. 23 3月, 2017 1 次提交
  7. 22 3月, 2017 5 次提交
  9. 21 3月, 2017 11 次提交
  11. 20 3月, 2017 5 次提交
  13. 18 3月, 2017 4 次提交
    • K
      Add assert that number of sort columns is 1 always for range in window · b533bcb2
      由 Karthikeyan Jambu Rajaraman 提交于 
      functions.

Coverity complains that the function `cmp_deformed_tuple` access the
datum from expression eval as an array. But we don't have that use case due to the
following error. For e.g., the parser will complain that it can't have
more than 1 columns for sorting when we use range in window function as shown below.

```
select depname, empno, salary, LAST_VALUE(salary)
error.
over (partition by depname order by empno, salary range
between 5000 preceding and 3900 preceding) as
highest_salary from empsalary;
ERROR:  only one ORDER BY column may be specified when RANGE is used in
a window specification
```
      b533bcb2
    • T
      Update paths for installers to avoid regexp match collisions · a848f1b3
      由 Tushar Dadlani 提交于 
      - In the current system, greenplum-db-appliance-(.*) collides with
  greenplum-db-(.*)
Signed-off-by: NTom Meyer <tmeyer@pivotal.io>
      a848f1b3
    • D
      Multi-dimensional arrays can now be used as arguments to a PL/python … (#1292) · eb1740c6
      由 Dave Cramer 提交于 
      * Multi-dimensional arrays can now be used as arguments to a PL/python function
(used to throw an error), and they can be returned as nested Python lists.

This makes a backwards-incompatible change to the handling of composite
types in arrays. Previously, you could return an array of composite types
as "[[col1, col2], [col1, col2]]", but now that is interpreted as a two-
dimensional array. Composite types in arrays must now be returned as
Python tuples, not lists, to resolve the ambiguity. I.e. "[(col1, col2),
(col1, col2)]".

To avoid breaking backwards-compatibility, when not necessary, () is still
accepted for arrays at the top-level, but it is always treated as a
single-dimensional array. Likewise, [] is still accepted for composite types,
when they are not in an array. Update the documentation to recommend using []
for arrays, and () for composite types, with a mention that those other things
are also accepted in some contexts.

The upstream patch is 94aceed3

* Give a hint, when [] is incorrectly used for a composite type in array.

    That used to be accepted, so let's try to give a hint to users on why
    their PL/python functions no longer work.

   see upstream 510e1b8e

* add tests for additional conversions.
move them into plpython_types
move the create function closer to the actual select
which is more like upstream
      eb1740c6
    • D
      Use available Makefile variables for src/bin · 34788e9a
      由 Daniel Gustafsson 提交于 
      Since we have a boolean yes/no switch for coverage enabled builds
in Makefile.global from autoconf, use that rather than inspecting
the CFLAGS for ease of reading the code. Also use the top_builddir
variable in setting the libdir, while unlikely to move in the
hierarchy it's the right thing to do.
      34788e9a