On Sun, 2005-03-13 at 01:31 +0100, Marc Santhoff wrote: > Am Sa, den 12.03.2005 schrieb Lawrence Harriott um 22:33: > > Hi Josh, > > I'm not, but I'll try to help... Sorry about the name Marc. Honest mistake. > > > By native I suspect you mean MyODBC. I get the exact same results using > > it as using unixODBC. Even the work around seems to work the same for > > both. > > There is a driver for PostgrSQL, look there: > > http://dba.openoffice.org/drivers/index.html I know, I have tried it. In fact, the gODBCConfig GUI that comes with MDK10.1 sets it up for you. It just doesn't work right. > > > Additionally, I have used the MySQL downloaded from MySQL and the one > > supplied with MDK10.1. Same results. I think at this point it is fair to > > say that the problems are not user errors. The ODBC interface between > > MySQL / Postgresql and OOo is defective. > > Not really. ODBC itself is some sort of a wasps nest. You have to: > - use version numbers of database and unixODBC/iODBC that "fit together" > - watch out for paths, the location of odbc.ini is compiled in, so the > best is to compile them yourself (/etc/odbc.ini, > /usr/local/etc/odbc.ini, ~/.odbc.ini, ...)
You obviously haven't tried that on MDK10.1, have you? I have a 12 hour marathon in my log with 98 entries resulting from trying to install a front end to MySQL called webyog (I think) when OOo and ODBC failed. The effort terminated in a circular dependency in two key development rpm's such that neither of them could be installed! Specifically,compiling the ODBC driver results in the compiler complaining about missing header files needed to compile the GUI. Take note of the circular rpm dependency matter I just mentioned. I compiled it without the GUI, and with a prefix to have the libraries installed in /usr/lib, and without a prefix to have it install to /usr/local/lib by default. The results are the same. I wrote all the parties concerned including Mandrake. Only OOo responded. Frankly, I am beginning to think of Mandrake as having or developing the attitudes of M$. It could not have cost them that much to even acknowledge receipt of the email. > - go step by step: test the db for access rights, do that over the local > net, test access with isql, then use applications Done all that and a few more. The isql and other tests work fine. Apparently any test outside of OOo seems to work ok. I had sorted out the permissions issue and even used the downloadable 'ignore privilege' macro. All this was done on the local net. Instructions followed exactly. There is a problem with the interface. There is no escaping that. So many users are not likely to be making the same trivial errors up to now. > > That's the reason why odbc is seen as flaky... > > > Had this not been the case, I > > do not think there would be such a massive effort to develop OOobase, > > the XML equivalent to M$ Access, when MySQL and Postgresql are clearly > > more mature, powerful and stable DBMS. > > You are free to choose. Agreed. I do welcome OOobase, don't get me wrong. But that does not provide a solution to the defective interface for people already using MySQL or Postresql. > > HTH, > Marc > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
