Subject | Re: [ib-support] Firbird 1 Release Version |
---|---|
Author | Claudio Valderrama C. |
Post date | 2002-03-15T01:41:18Z |
"Raf Schandevyl" <Raf.Schandevyl@...> wrote in message
news:3C90A255.3020908@......
I've not seen the error myself, but I really love your explicit clue. Why
can't other people do the same? The problem should be with blobs, then. I
was trying to figure out how a field could be longer than the allowed
implementation or DSQL would have complained already at creation time. Blob
handling's the path that should be tracked inside the engine.
If the issue is not as easy as simply creating a procedure that returns a
blob in an output param and do backup/restore, please reply.
I don't intend to explain still what I fixed that caused such a side effect.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing
news:3C90A255.3020908@......
> Since I installed the latested version i've problems with my storedRaf:
> procedures returning blob variables.
>
> I'm getting the following error when restoring the database.
>
> Implementation limit exceeded.
> block size exceeds implementation restriction.
I've not seen the error myself, but I really love your explicit clue. Why
can't other people do the same? The problem should be with blobs, then. I
was trying to figure out how a field could be longer than the allowed
implementation or DSQL would have complained already at creation time. Blob
handling's the path that should be tracked inside the engine.
If the issue is not as easy as simply creating a procedure that returns a
blob in an output param and do backup/restore, please reply.
I don't intend to explain still what I fixed that caused such a side effect.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing