Re: MySQL and PG (was Dr. Miguel....)
Re: MySQL and PG (was Dr. Miguel....)
- Subject: Re: MySQL and PG (was Dr. Miguel....)
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 21 Dec 2009 10:00:09 -0500
Most likely it is connection refused ..... try ssh'ing into the server
that the wo app is deployed on and try and log into the database using
the same credentials as the app does from the wo server.
mysql -u <wouser> -h <mysqlhost> -p<wopassword>
(Note no space between -p and <password> when u provide the passwod in
cleartext on the command line. Alternatiovely u can do it this way and
type the non-echoed password:
mysql -u <wouser> -h <mysqlhost> -p
Password:
Remember MySQL always uses THREE credentials the authenticate. The
user, password AND client hostname. If I want all wo machines on a
local subnet to have access toa database, I might do sth like this
using % wildcard:
GRANT SELECT, INSERT, UPDATE, DELETE ON mydatabase.* TO
'wouser'@'192.%' IDENTIFIED BY 'wopassword';
HTH, Kieran
On Dec 20, 2009, at 11:37 PM, Daniel Beatty wrote:
Greetings gang,
Ok, I have a mystery that I am tracking down, and I need some
help. I have a MySQL database that seems to work for Wonder's D2W
under Eclipse. However, deployment seems to be another issue. The
eomodel for the deploy and Eclipse development environment are the
same. Yet in the deployment case, I get the following error:
java.lang.IllegalStateException: _obtainOpenChannel --
com.webobjects.eoaccess.EODatabaseContext
com.webobjects.eoaccess.EODatabaseContext@3bea817f: failed to open
database channel. Check your connection dictionary, and ensure your
database is correctly configured.
Any ideas?
Thank you,
Dan Beatty, M.S. CS (B.S. EECS)
Ph.D. Student
Texas Tech University
email@hidden
http://venus.cs.ttu.edu/~dabeatty
http://web.me.com/danielbeatty/My_Home_Page/Welcome.html
On Dec 3, 2009, at 7:50 PM, Andrew Lindesay wrote:
Hello Guido;
I have to concur; PG has been really great for me and I have had
some problems with MySQL. The most serious problem with MySQL was
memory-exhaustion in the driver, but the latest MySQL driver has
seemed to _finally_ resolved that one. I have to also concur with
Mike though in that I did try to take pgpool (replication only) to
a production environment and it was not a happy morning and I had
to roll it back. If I had to choose between the two for a small
WOA, I would definitely lean towards PG because of the trouble-free
operations I've experienced. I notice there are a number of
companies offering support for larger PG deployments.
cheers.
I don't think I ever used MyISAM tables with a WO app. I have seen
corrupted data with InnoDB tables and WO usage though. For the
rest, they might have been MyISAM used from some PHP web crap, but
the thing is: the SQL stored the thing and some historic data gets
corrupted. That was the issue we had. I can't recall exactly
enough to blame it completely on MySQL, but I stopped using it and
I had never ever again any issues with corrupt data (95%
PostgreSQL, 5% FrontBase usage).
FrontBase has the issue that you can easily kill the server with
bad input. This can't happen with PostgreSQL as you get your own
backend for each connection.
Between the three databases MySQL, PostgreSQL, and FrontBase, I've
used PostgreSQL the most and with the most success and least
amount of trouble. I'd love to see a multi master clustering
solution for it though that actually works and is not a piece of
shit.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden