comp.databases.mysql Google Group

Re: Socket Server with MySQL

2009-11-28T02:03:42Z

That will make the code work well with MySQL but bad with
other databases. If the intent is to write database independent
code, then it is not an optimal solution.
Arne

Re: Socket Server with MySQL

2009-11-28T02:01:27Z

RVic wrote:
From the practical perspective then I think that:
* if you do not use a connection pool, then you should
send a SELECT 1 every hour to keep things alive
* if you do use a connection pool, then you should
use one capable of verifying connections and return
a valid to you (and if your connection pool does not

Re: Full outer join?

2009-11-27T22:01:59Z

Eggzaggly.

Re: Full outer join?

2009-11-27T21:59:06Z

On Nov 27, 12:49 pm, "David Portas"
So use UNION ALL

Re: Full outer join?

2009-11-27T20:49:17Z

Unfortunately the given workarounds using UNION are not truly FULL OUTER
joins because they eliminate duplicate rows that a real full outer join
would not. In most cases that maybe won't be a problem but I think it's just
worth noting that reproducing the true behaviour of FULL is a bit more
complex than those examples imply.

Re: Complex query on tree structure: Help!

2009-11-27T16:53:24Z

This might not count as a single query, but if you know its never more than
5 deep (which you said) then you could do it in 5 queries (one for each
level of depth) and use union to combine the results.

Re: difficult query...for me

2009-11-27T14:07:05Z

Still completely unnecessary - and does not create a historical report.

Re: difficult query...for me

2009-11-27T14:05:40Z

So a second troll shows up. I respond to trolls in the only language
they understand.

Re: Complex query on tree structure: Help!

2009-11-27T11:36:05Z

Many thanks Andrew, but I already had those!
No, after 4 hours of beating my brains I ended up doing it the long way,
which took ten minutes to code!
I ended up with a two dimensional matrix, and simply walked through that
inserting numbers that are not null, and not already in, into a PHP array.
$result=mysql_query(sprintf(

Re: difficult query...for me

2009-11-27T08:37:33Z

Franz:
Still, I wonder if this is really necessary for historical reports,
UNLESS you also remove historical data.
In case you always have the required data in your database, a
historical report could simply be produced using something like
SELECT a,b,c FROM table
WHERE dateA > "2007-01-00" AND dateA < "2008-12-99"

Re: difficult query...for me

2009-11-27T08:27:13Z

Richard ha scritto:
historical report IS the reason I was asking suggestions for.
Thanks for your partecipation.
Franz

Re: Complex query on tree structure: Help!

2009-11-27T07:47:44Z

[..]
I don't have much experience in this area, but I do have a couple of links
in my bookmarks just in case someone springs the requirement for
hierarchical data on me at short notice... ;-)
[link]
[link]

Re: difficult query...for me

2009-11-27T07:11:05Z

Jerry Stuckle:
Darn, Jerry!
Is it really necessary to go in this direction with every second thread?
Certainly, many technical experts know a lot, but at the same time have
difficulties communicating 'nicely'. However, it isn't absolutely
required to make it so obvious who qualifies for this group.

Re: difficult query...for me

2009-11-27T02:18:16Z

I love you too, Jerry.
Yours,
R.

Re: difficult query...for me

2009-11-27T01:29:38Z

There are things to look to avoid in ANY database design. This is one
of them.
Spoken like someone who's looking for excuses for poor design.
That is not the reason here, though, is it. But in any case, that's
still not a reason to store a sum.
Yep, it's easy for incompetent idiots to shout from a distance. Now,