Re: [ADMIN] Cannot retrieve images inserted through VB and odbc, after a table reorganization.

Hi Craig,

I’m reloading into the very same database.
If I insert a new row into the table (through VB/ODBC), I’m able to retrieve it (again from VB). But if after inserting the new row, I do a reorg of the table (eg. with a “cluster table”), I’m no longer able to retrieve that same row. In short, as long as the newly inserted rows are not “re-written” in some way, they can be retrieved through VB/ODBC.

Alanoly.

From: Craig James [mailto:cjames(at)emolecules(dot)com]
Sent: Wednesday, September 03, 2014 12:13 PM
To: Alanoly Andrews
Cc: pgsql-admin(at)postgresql(dot)org; pgsql-general(at)postgresql(dot)org
Subject: Re: [ADMIN] Cannot retrieve images inserted through VB and odbc, after a table reorganization.

On Wed, Sep 3, 2014 at 8:13 AM, Alanoly Andrews <alanolya(at)invera(dot)com<mailto:alanolya(at)invera(dot)com>> wrote:
We have an issue with images (TIFF files) that are loaded into a postgres database table (where the image field is defined as type “lo”). The code to load the images is written in VB and the connection to the database is through postgres odbc installed on the PC. All images inserted through the VB program are retrievable also through odbc/VB, as long as the table rows at the backend are not reorganized in any way. If the table data is unloaded/reloaded or clustered (on an index) or reloaded through a pg_dump and restore, then on trying to retrieve the images, the VB program gets the error : “Multiple-step OLE DB operation generated errors. Check each OLE DB status value……etc”.

The data in the backend database is still readable through other image retrieval programs connecting directly to the server (not through ODBC or VB).

Are you reloading into the very same database, or into a different one? Your question doesn't make it clear. If you're loading into a new database, then one thing that comes to mind is that the bytea_output parameter in postgresql.conf might be different on the second database.

Craig

The database is on an AIX server (version 6.1). Postgres version is 9.1.4.

I’d welcome any input towards the resolution of this problem.

Thanks.

Alanoly Andrews
alanolya(at)invera(dot)com<mailto:alanolya(at)invera(dot)com>

________________________________
If you no longer wish to receive any of our emails, click on UNSUBSCRIBE.<mailto:unsubscribe(at)invera(dot)com?subject=***Unsubscribe***> This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.

Si vous ne désirez plus recevoir de nos courriels, veuillez appuyer sur DÉSABONNEMENT.<mailto:unsubscribe(at)invera(dot)com?subject=***Unsubscribe***> Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen.

--
---------------------------------
Craig A. James
Chief Technology Officer
eMolecules, Inc.
---------------------------------

________________________________

If you no longer wish to receive any of our emails, click on UNSUBSCRIBE.<mailto:unsubscribe(at)invera(dot)com?subject=***Unsubscribe***> This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.

Si vous ne désirez plus recevoir de nos courriels, veuillez appuyer sur DÉSABONNEMENT.<mailto:unsubscribe(at)invera(dot)com?subject=***Unsubscribe***> Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen.