LOL, look what I've got after posting
to one of the groups about my problem with
multiple JOIN query...Some kind of robot
reads one of them?
Original Message
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Precedence: bulk
Subject: Catalog listing
To: [EMAIL PROTE
Jeremy Peterson wrote:
> I haven't tested this code, but it should get you started. I imagine that
> you have a lot of different days that you are trying to restrict in your
> query (This could be costing you a lot of time), so the first query removes
> all articles you don't want up front befor
Jeremy Peterson wrote:
> Could you repost your original message (I deleted it already, sorry.) and
> more details about your database tables even some sample data. I'll try to
> make more sense of the query you are performing and help you along.
>
> In general it would be better to eliminate t
Jeremy Peterson wrote:
> If you are concerned with speed, consider multiple queries. Joins cause
> most delays. Give that a shot.
What do you mean? Sorry, please explain
futher, I don't know what you have in mind...
I have to do some of those joins, because of
the relationships betw
I need help width formulating the most
effective (in terms of processing time)
SQL query to count all the "new"
documents in the repository, where "new" is
defined as "from 00:00:01 up to 23:59:59
today". My current query does not give me
satisfactory results, it creates a v
"CPT John W. Holmes" wrote:
> From: "Adam i Agnieszka Gasiorowski FNORD" <[EMAIL PROTECTED]>
>
> > I cannot use this query
> >
> > CREATE TABLE table LIKE other_table;
> >
> > , which is supposed to create an
> > empty "c
I cannot use this query
CREATE TABLE table LIKE other_table;
, which is supposed to create an
empty "clone" of the other_table named
table.
Was it added in some later MySQL version?
It's in the manual on mysql.com, bo no version info
available.
--
Seks, seks
Kim Steinhaug wrote:
> Then I query the mySQL database again to get the final result set, which
> I return together
> with the buildt prev/next htmlkode
Instead of querying twice, use the
SQL_CALC_FOUND_ROWS parameter of SELECT
statement and then do a quick
SELECT HIGH_PRIORIT
