public.commandprompt.com: Issueshttps://public.commandprompt.com/https://public.commandprompt.com/favicon.ico?16484970162009-04-29T11:22:37Zpublic.commandprompt.com
Redmine Simpycity - Bug #5000 (New): Automatic Rollback Fix.https://public.commandprompt.com/issues/50002009-04-29T11:22:37ZLacey Powerslacey.powers@commandprompt.com
<p>Simpycity doesn't always issue a rollback for some transactions, such as failed functions.</p>
<p>This should be fixed, and an appropriate test case created to verify the fix and test in future releases.</p> Pggraph - Bug #4960 (New): pg error of pggraph_2_2https://public.commandprompt.com/issues/49602008-12-30T09:09:04ZDevrim Gunduzdevrim@commandprompt.com
<pre>
pggraph_2_2 2008-12-30 09:15:22 PST 24681 ERROR: permission denied to set parameter "log_duration"
</pre> 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> Pggraph - Bug #4949 (New): Document behaviourhttps://public.commandprompt.com/issues/49492008-07-17T16:59:08ZAurynn Shawashaw@commandprompt.com
<p>When date start and date end are used, it defaults to the range behavior.</p>
<p>When neither are selected, it defaults to the previous behavior, which is now() - interval time.</p> Pggraph - Bug #4948 (New): in pggraph_table, prevent crash if no tables presenthttps://public.commandprompt.com/issues/49482008-07-16T21:42:46ZAurynn Shawashaw@commandprompt.com
<p>If a given database doesn't have any tables, and it is the default in pggraph_table.py, then we need to catch that and switch to a different database/datname.</p> Pggraph - Bug #4947 (New): Do testing of data arrayshttps://public.commandprompt.com/issues/49472008-07-16T21:01:03ZAurynn Shawashaw@commandprompt.com
<p>While generating date range pages, we should test the length of each return set, so that we can trim out offsets that are going to be no-shows.</p>
<p>This is going to be kind of expensive to do for every page refresh, but I feel it's <br />worthwhile.</p>
<p>Alternatively, just have "NO DATA" splayed over the image in the event that there's no data.</p>
<p>How should we approach this?</p> Pggraph - Bug #4945 (New): Force all graphs to abort if non-specific data specifiedhttps://public.commandprompt.com/issues/49452008-07-15T15:32:45ZAurynn Shawashaw@commandprompt.com
<p>For all graphs, prevent date ranges from working if:</p>
<ul>
<li>High-level, multi-graph pages would be generated normally</li>
<li>Non-specific data is passed to the graphing function.
<ul>
<li>For pggraph_database, it REQUIRES a datname</li>
<li>For pggraph_table, it requires a datname, a tablename and a schemaname</li>
<li>For pggraph_index, it requires a datname, an indexname, and a schemaname</li>
</ul></li>
</ul> Pggraph - Bug #4940 (New): Remove prefixeshttps://public.commandprompt.com/issues/49402008-07-14T11:05:46ZAurynn Shawashaw@commandprompt.com
<p>As we are moving to a schema'd design, remove the prefix additions from the code and all new installations.</p>
<p>This involves a plpgsql function signature change.</p>