Bob Terrell wrote:
> So there you go. Give it a shot and see if it runs any faster. If you need the time,
> replace that first test in the WHERE clause with the one mentioned above. If this is
> run often (or if it just takes a _really_ long time), put an index on the date
> field, if one isn'
Bob Terrell wrote:
> on 1/2/04 12:59 PM, Adam i Agnieszka Gasiorowski FNORD wrote:
>
> Thanks for the info. Just so I'm sure I know what I should: :)
Thanks for your answer, very helpful!
> > > $suma = 0;
>
> For starters, you won't need this
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
Bob Terrell wrote:
> on 1/2/04 12:59 PM, Adam i Agnieszka Gasiorowski FNORD wrote:
>
> > Tell me if you need any additional information.
> > Thank you for all your help.
>
> Some additional information would help, yes. What exactly are the sections, for
> examp
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
Do you know if there ever will be
possibility to not only match with REGEXes,
but also SELECT with them? Sth like
SELECT REGEX(']+>', x_article.Content) FROM ...
--
Seks, seksić, seksolatki... news:pl.soc.seks.moderowana
http://hyperreal.info { iWanToDie } WiNoNa) (
http://s
