much of a pain for me.
Disclaimer: I'm not a real MySQL expert, or anything. There could be
ways of getting around this, but after two weeks of trying, I decided
to give up. It only took me a few hours to build the requisite
PostgreSQL scripts and I never looked back.
Adam Ruth
On Feb 2
Wow, I didn't know that (didn't get far enough to test any rollback).
That's not a good thing. facetiousBut then again, it's MySQL who
needs rollback anyway?/facetious
On Feb 2, 2004, at 5:44 PM, Christopher Kings-Lynne wrote:
One more thing that annoyed me. If you started a process, such
of the
schemas at once, that has proven quite useful.
We, however, did have a need to periodically select data from 2
schemas
at a time, and it was simpler logic than if we needed 2 database
connections.
Adam Ruth
On Mar 22, 2004, at 2:30 PM, Subbiah, Stalin wrote:
--sorry to repost, just subscribed
select data from 2 schemas
at a time, and it was simpler logic than if we needed 2 database
connections.
Adam Ruth
On Mar 22, 2004, at 2:30 PM, Subbiah, Stalin wrote:
--sorry to repost, just subscribed to the list. hopefully it gets to
the
list this time --
Hi All,
We are evaluating the options
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
You could try changing the IN to an EXISTS, that may alter how the
optimizer weighs the limit.
SELECT ID FROM ps_image WHERE EXISTS (SELECT null FROM
ps_gallery_image WHERE gallery_id ='G7ejKGoWS_cY' and image_id =
ps_image.id) ORDER BY LOWER(FILE_NAME) ASC
On 30/04/2009, at 3:51 AM,
