{5} Assigned, Active Tickets by Owner (Full Description) (11 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
jtv
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #34 | Pipelines, variables, and prepared statements | other | 3.1 | defect | major | 02/13/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When a pipeline is operating on a transaction, it won't be possible to issue queries on the fly underneath the libpqxx API. This will break some existing features that may issue queries at unexpected moments:
Perhaps the simplest solution would be to drain any existing pipeline first. Still, that may create new complications. Another approach is to insert a new layer into internal command execution that goes through an existing pipeline if needed. Even things like transaction bracketing could be layered on top of that (so perhaps subtransactions could be made to work inside pipelines!) and perhaps this layer could be instructed to allocate a temporary pipeline if none is active. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #97 | Array support | datatypes | 3.1 | enhancement | normal | 01/19/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Joris van Zwieten requests support for postgres array types. At the moment arrays can only be manipulated and queried in SQL, or generated and parsed as text. It would be nice to help users get around the latter if we can. Container and stream interfaces seem the most appropriate. We'd want to be able to construct input arrays from either a field or a string. There are a few gotchas:
Finally there is the encoding problem in the case of arrays of strings (or arrays of arrays of strings etc.). Parsing a string as an array of strings can go haywire in multibyte encodings that allow byte values equivalent to the closing quote inside a multibyte character. To get around that we'd need to know at least where the character boundaries are--which in turn depends on the encoding being used. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #4 | Multi-line copy support | performance | enhancement | normal | 12/27/05 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See feature request 1374 on the old project site for details. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #86 | fieldstream outputs escaped bytea data | other | defect | normal | 10/07/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I was looking for a way to retrieve bytea data from a result without copying it. I tried to use fieldstream using libpqxx-2.6.8 but I got escaped data. I don't know it it's a bug (I hope so). If it is not, how do I retrieve bytea data without using much more than bytea data size of memory? This is roughly code I used: result R;
...
pqxx::fieldstream file_data(R.at(0)["file_data"]);
#define CACHESIZE (0x7fff) /* minimum POSIX limit for read cache size */
char data_cache[CACHESIZE];
ofstream out;
out.exceptions(ofstream::failbit | ofstream::badbit);
out.open("filename", ios::binary);
while ( file_data.good() && out.good() ) {
file_data.read(data_cache, CACHESIZE);
out.write(data_cache, file_data.gcount());
}
out.close();
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #155 | Test failures on Solaris 10 for libpqxx-2.6.9 | test | defect | normal | 08/21/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Good Afternoon. I've configured and built libpqxx-2.6.9 on Solaris 10. However, 2 tests are failing. These are test064 and test089. The postgres libraries available on the Solaris10 is 8.3.3 The database to which the tests are being directed is 8.1.9 (on a different server with different OS). This the output for test064:
This is the output for test089
I'll be happy to provide what information is desired. Oh - grep is 2.5.1, g++ is 3.4.6 (also have 3.4.3). Thanks, Ryan |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #171 | Compilation of the vc-test.mak fails on VC8.0 WindowsXP | test | defect | normal | 11/10/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Using MSVC8.0 on WindowsXP, I compiled succesfully postgresql8.3.5, and also compiled successfully libpqxx as the command "nmake /f win32/vc-libpqxx.mak ALL" has not reported any error: in fact all the compilation went fine up to the paragraph in win32/INSTALL.txt: "After that, it is recommended that you compile and run the self-test programs included in the package. ...." After that, the problem is that when I try to compile the test suite I get: F:\libpqxx-3.0>nmake /f win32\vc-test.mak ALL Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 Copyright (C) Microsoft Corporation. All rights reserved. NMAKE : fatal error U1073: don't know how to make 'runner' Stop. I tryed to regenerate the vc-test.mak file from its template in vc-test.mak.template with the tools/template2mak.py, but the resultant file is identical (only some slashes became back slashes :)) How to fix this problem and run the tests? Thanks, Luca |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #32 | Test nul character handling in large objects | test | 3.1 | defect | normal | 02/11/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
One of the large-object tests should verify that nul bytes are handled correctly wherever feasible. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #52 | Move installation docs out of README | documentation | enhancement | normal | 05/14/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The README is getting uncomfortably long, and it would be nice to have somewhat richer markup in that file. This ought to be done on the wiki, and exported as HTML for inclusion in the distribution archive. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #53 | Move tutorial to wiki | documentation | enhancement | normal | 05/14/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The tutorial is now written in DocBook; it's too hard to maintain, and for some reason has encoding problems on the home site. Move it to Wiki, integrate with installation docs taken from README (see #52), and convert to HTML for inclusion in the distribution archive. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #66 | Support and use PQescapeIdentifier() | other | defect | normal | 06/15/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A new libpq function has been proposed, PQescapeIdentifier(), that will escape strings for use in identifiers (rather than for use in strings as the PQescapeString() functions do). Once this happens, we should use it for cursors and other objects that the client program can suggest names for; and probably we should export the function as well. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #29 | Phase out TODO file | site | defect | normal | 02/11/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The items in the TODO file properly belong in the bug tracker. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
