public.commandprompt.com: Issueshttps://public.commandprompt.com/https://public.commandprompt.com/favicon.ico?16484970162014-05-11T09:24:00Zpublic.commandprompt.com
Redmine postgres_fdw - Bug #5303 (New): [SPAM] Good shoes good priceshttps://public.commandprompt.com/issues/53032014-05-11T09:24:00ZAlvherre -dntnmh@dng.vnn.vnPL/php - Feature #5259 (New): Add support for anonymous DO blocks.https://public.commandprompt.com/issues/52592011-05-27T05:52:31ZAlexey Klyukinalexk@commandprompt.com
<p>PostgreSQL 9.0 introduced a notion of inline DO blocks:<br /><a class="external" href="http://www.postgresql.org/docs/9.0/interactive/sql-do.html">http://www.postgresql.org/docs/9.0/interactive/sql-do.html</a></p>
<p>So far, nothing stops us from adding support for such blocks written in PL/PHP.</p> PL/php - Bug #5258 (New): Get rid of the trusted PL/PHPhttps://public.commandprompt.com/issues/52582011-05-27T05:43:07ZAlexey Klyukinalexk@commandprompt.com
<p>Apparently, the trusted PL/PHP has lots of security problems due to its trusted status, from sharing the same interpreter with an untrusted one, to <br />the fact that the trusted implementation relies on PHP safe mode, which is deprecated and allows some 'untrusted' (in PG's sense) operations, i.e. filesystem/network access. ATM we need to get rid of PL/PHP and leave only PL/PHPU implementation.</p> PL/php - Bug #5255 (New): support TRUNCATE triggershttps://public.commandprompt.com/issues/52552011-05-21T16:29:20ZÁlvaro Herreraalvherre@commandprompt.com
<p>$SUBJECT</p> PL/php - Bug #5225 (New): Unable to build PL/php on OS X (PHP 5.3)https://public.commandprompt.com/issues/52252010-06-29T05:25:59ZAlexey Klyukinalexk@commandprompt.com
<p>On OS X embed is built as a bundle instead of a library, making it impossible to link against it.</p>
<p>I've submitted the problem to the PHP project:<br /><a class="external" href="http://bugs.php.net/bug.php?id=48318">http://bugs.php.net/bug.php?id=48318</a></p>
<p>Still, it's not possible to build PL/php at the moment on this platform.</p> Simpycity - Bug #4993 (New): Finish docshttps://public.commandprompt.com/issues/49932008-11-25T11:31:41ZAurynn Shawashaw@commandprompt.com
<p>Finish docs</p> Pggraph - Bug #4959 (New): Upgrade all present pggraph clients to pggraph_2_2https://public.commandprompt.com/issues/49592008-07-28T08:07:29ZAurynn Shawashaw@commandprompt.com
<p>As description. This should be doable with a simple upgrade script. I'd think about 4 hours to throw the script together.</p> Pggraph - Bug #4958 (New): Fix the "Help I have no data" problem with pggraph.https://public.commandprompt.com/issues/49582008-07-25T11:37:31ZAurynn Shawashaw@commandprompt.com
<p>Make a moving window when trying to establish the datnames &c in the tables.</p> Pggraph - Bug #4956 (New): dbrollup.py needs to support pggraph 2.2https://public.commandprompt.com/issues/49562008-07-25T08:02:24ZAurynn Shawashaw@commandprompt.com
<p>Per <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: 1-hour bug broken on v2.2 installs (Closed)" href="https://public.commandprompt.com/issues/4953">#4953</a> and the 1-hour bug, dbrollup.py needs to be updated for pggraph 2.2 to support the new table, table structure, and different location of the pggraph_clients data.</p> Pggraph - Bug #4954 (New): pggraph_clientshttps://public.commandprompt.com/issues/49542008-07-25T07:59:35ZAurynn Shawashaw@commandprompt.com
<p>for pggraph 2.2, the create_owner_tables function in the installer needs to create a pggraph_clients table that stores data about pggraph client installs for the rollup/averaging function.</p>
<p>This is not presently created by the installer.</p> Pggraph - Bug #4952 (New): Help interfacehttps://public.commandprompt.com/issues/49522008-07-21T10:40:30ZAurynn Shawashaw@commandprompt.com
<p>Come up with a mechanism to provide "help" tooltips as needed for various form elements. Decouple from existing templates and code, figure out a mechanism/library to handle it.</p> Pggraph - Bug #4951 (New): Document date range behaviourhttps://public.commandprompt.com/issues/49512008-07-21T10:38:00ZAurynn Shawashaw@commandprompt.com
<p>As title - document how pggraph will function in Date Range mode, as well as out of Date Range mode.</p> Pggraph - Bug #4950 (New): Write unit testshttps://public.commandprompt.com/issues/49502008-07-17T17:02:20ZAurynn Shawashaw@commandprompt.com
<p>This is pretty obvious</p> PL/php - Bug #4972 (In Progress): array PHP <-> Pg conversion is brokenhttps://public.commandprompt.com/issues/49722005-11-23T11:48:44ZÁlvaro Herreraalvherre@commandprompt.com
<p>Element parsing in arrays can easily be confused. Test case:</p>
<pre>
create or replace function another_text_test(text[], int)
returns text language plphp as $$ return $argsr0[$argsr1]; $$;
</pre>
<p>Strings should be quoted before passing them to PHP, so the NOTICE from PHP here is bogus:</p>
<pre>
pl_regression=# select another_text_test($${"foo",'bar', "{"}$$, 0);
NOTICE: plphp: Use of undefined constant foo - assumed 'foo'
another_text_test
-------------------
foo
(1 fila)
</pre>
<p>The same reason causes this to "eat" the inner level of quotes:</p>
<pre>
pl_regression=# select another_text_test($${"'bar'", "{"}$$, 0);
another_text_test
-------------------
bar
(1 fila)
</pre>
<p>Note particularly this totally unexpected behavior:</p>
<pre>
pl_regression=# select another_text_test($${"'bar'", "{"}$$, 1);
another_text_test
-------------------
array(
(1 fila)
</pre> PL/php - Feature #4967 (In Progress): Redesign memory handlinghttps://public.commandprompt.com/issues/49672005-11-16T17:31:06ZÁlvaro Herreraalvherre@commandprompt.com
<p>Currently memory is not handled very well. It would be nice if we had one MemoryContext for each function that could be automatically reset or deleted when the function is recompiled. Additionally we would need a compilation context, and maybe an execution context as well.</p>