Bug 117186
Summary: | Open office has lost read access to odbc DB | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Need Real Name <mike> |
Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-12-09 12:45:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 114963, 123268, 136451 |
Description
Need Real Name
2004-03-01 13:14:16 UTC
Further info I have tested the Database/odbc driver with excel/access and everything works fine. *** Bug 117190 has been marked as a duplicate of this bug. *** caolanm->mike.uk: What's your unixODBC rpm version ? Can you try with a unixODBC >= 2.2.8 ? openoffice.org-1.1.2-11.5.fc3 unixODBC-2.2.10-1 postgresql-7.4.6-1.FC3.1 > su - postgres > createuser Enter name of user to add: cmc Shall the new user be allowed to create databases? (y/n) y Shall the new user be allowed to create more new users? (y/n) y CREATE USER > exit > su - cmc > createdb CREATE DATABASE > su cat > /etc/odbc.ini [PostgreSQL-test] Description = Postgres database test ReadOnly = 0 Servername = localhost Database = cmc Port = 5432 Driver = PostgreSQL Protocol = 7.4.6 UserName = cmc Password = ^D > exit > oowriter & tools->data sources new data source, database type ODBC, select PostgreSQL-test successfully add a table with some random column types can view and edit database create a simple query, can run it and can still edit afterwards exit oowriter, restart, still ok I suspect that it might have been a problem with unixODBC, I can't reproduce a similiar problem on FC-3. Though if theres another way to reproduce this, feel free to reopen. |