It sounds like you want to parse the contents of the bytea column within
a trigger/stored procedure. I haven't done this myself (I process the
bytea data in java as an input stream after retrieving it from
postgres), but you could probably use a FOR loop over the bytea column
and then use some com
What I am needing to do is to store a file I receive, say file1.dat. I want
to store file1.dat into a bytea field so we can always go back and retrieve
the original file to verify if needed. However, I also need to process the
data that is in file1.dat (1234 johnny 1254.12). When I load file1.d
Chris Hoover escribió:
> No, I need to store the entire file as received into the database.
Then you original question does not make any sense to me, because if you
pass the entire file content, why would Postgres *not* be able to read
it?
> On 4/11/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
No, I need to store the entire file as received into the database.
Chris
On 4/11/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Chris Hoover escribió:
> Hopefully a quick question.
>
> If I store a file into a bytea field, is there anyway for postgres to
read
> the contents of the file?
When y
Chris Hoover escribió:
> Hopefully a quick question.
>
> If I store a file into a bytea field, is there anyway for postgres to read
> the contents of the file?
When you say "store a file", do you mean "store a filename"?
> Here is my scenario:
>
> Receive text file
> insert file into bytea fiel
Hopefully a quick question.
If I store a file into a bytea field, is there anyway for postgres to read
the contents of the file?
Here is my scenario:
Receive text file
insert file into bytea field
insert trigger fires
- read file contents
- post contents into production tables
Is this at all
