Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Invalid Blob ID" on Firebird Super Server 2.1.0.17798-0 [CORE1874] #2305

Closed
firebird-automations opened this issue Apr 29, 2008 · 9 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: HCN (hcn)

I´m receiving the exception "Invalid Blob ID" after updating a record on a table that has a blob field. It´s happens even if I didn´t modify the content of the Blob.

I know this was a know issue on 2.1 RC. Wasn´t it solved on 2.1 final?

I just upgraded from 1.53 to 2.1 and this exception starts. The bigest problem is that now, I can´t rollback to FB 1.53 or 2.0 anymore because de database ODS was already updated to 11.1.

Best regards,

    HCN
@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Which issue ? Where the test case ?

You can downgrade to 1.5 or 2.0 via backup and restore on target server if you don't recompile objects or via data pump and metadata script if you didn't used new 2.1 features. Ask details in support list.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

You never heard of *testing* an application/database before migrating to a new version?

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Please take into account that it's impossible to solve a problem with a description you've provided. Please read
http://www.firebirdsql.org/index.php?op=devel&sub=qa&id=bugreport_howto
and adjust your bug report if you want it to be fixed.

@firebird-automations
Copy link
Collaborator Author

Commented by: HCN (hcn)

"Which issue ? Where the test case ? "

Bug report updated. I didn´t supply you with more details because I saw this problem on core-1342 and core-1417, both on 2007, so I imagined it was already know Issue... Sorry.

"You never heard of *testing* an application/database before migrating to a new version? "

Dear Sean, I did the tests, but sometimes is quite difficult to test all possibilities... you should know it, or the programs you develop and test are 100% bug free?... Ohw my God, we have a SUPER PROGRAMMER HERE !!!

@firebird-automations
Copy link
Collaborator Author

Modified by: HCN (hcn)

description: I know this was a know issue on 2.1 RC. Wasn´t it solved on 2.1 final?

I just upgraded from 1.53 to 2.1 and this exception starts. The bigest problem is that now, I can´t rollback to FB 1.53 or 2.0 anymore because de database ODS was already updated to 11.1.

Best regards,

    HCN 

=>

I´m receiving the exception "Invalid Blob ID" after updating a record on a table that has a blob field. It´s happens even if I didn´t modify the content of the Blob.

I know this was a know issue on 2.1 RC. Wasn´t it solved on 2.1 final?

I just upgraded from 1.53 to 2.1 and this exception starts. The bigest problem is that now, I can´t rollback to FB 1.53 or 2.0 anymore because de database ODS was already updated to 11.1.

Best regards,

    HCN 

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

> Bug report updated. I didn´t supply you with more details because I saw this problem on core-1342 and core-1417, both on 2007, so I imagined it was already know Issue

Both reports you refered to is fixed in v2.1 beta 2. You may see it in coresponding tickets details.
You still not provided any test case or details about your issue.
Without it its impossible to do something.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

No test case provided upon request.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Incomplete [ 4 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant