Bug 84387 - unexpected error: cannot find path component
unexpected error: cannot find path component
Product: Red Hat Database
Classification: Red Hat
Component: gui (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Fernando Nasser
Permaine Cheung
Depends On:
  Show dependency treegraph
Reported: 2003-02-15 07:33 EST by Erwin
Modified: 2013-11-19 14:19 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-17 09:47:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erwin 2003-02-15 07:33:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
While using RHDB administrator I get 'unexpected errors'.
It says Can't find path component.

Version-Release number of selected component (if applicable):

How reproducible:
Couldn't Reproduce

Additional info:

I am running Postgres 7.3
PS: I cannot copy the error to clipboard!
Comment 1 Fernando Nasser 2003-02-17 09:47:28 EST
Hi Erwin,

I've tried to find the source of this message in the source code and could not
find it.  Without proper instructions on how to reproduce it it will be
impossible to figure out what went wrong.

But please not that the rhdb-admin program that is out there was tested with the
Red Hat Database Release 2.1, which includes the PostgreSQL 7.2.3 backend.

Although it may work with a PostgreSQL backend 7.3, we haven't tested it as this
combination is not part of any RHDB release.  We will soon have an alpha version
of the rhdb-admin program that works with PostgreSQL 7.3 (it is aware of
SQL-Schemas) and has many new features.  Monitor the sources.redhat.com/rhdb web
site onthe last week of February.

I am closing your report as there is nothing we can do about it.  But thanks for
taking the time to report it anyway.

Best regards,

Note You need to log in before you can comment on or make changes to this bug.