Re: ORDER BY RAND() performance

2004-03-08 Thread Neil Gunton
Donny Simonton wrote: > > Neil, > We never delete from primary tables. No questions asked! We would just > mark a entry as deleted, and not select from it. > > Another option you can do to solve your deletion problem is, select 35 rows > for example, when you really only want 30. That way, you

Re: ORDER BY RAND() performance

2004-03-08 Thread Neil Gunton
Donny Simonton wrote: > One other option that we use > sometimes is say you need 30 results randomized, and you have an > auto-increment in your table. Create 30 random numbers, then do a select > with something like this: > > Select * from blabla where lkajsdlkjas IN (10, 43, 22, 8981, etc...) >

Re: ORDER BY RAND() performance

2004-03-08 Thread Neil Gunton
Ray wrote: > an alternative to the order by rand() with large record sets is to > pick a random starting point "limit $randPoint, 30" don't know if > its a viable solution to your situation, but it limits you to 2 > querys (row count, fetch) rather then the 30 (fetch 1 x 30) Thanks! I did see thi

Re: ORDER BY RAND() performance

2004-03-08 Thread Neil Gunton
[EMAIL PROTECTED] wrote: > > If your infact (sounds like) storing the pictures meta-data (name, size, > owner, etc) and the data (blob of some kind) .. I would definately break > up the design into 2 tables. That way when dealing with the meta-data > table (your RAND() query) there is much less d

ORDER BY RAND() performance

2004-03-08 Thread Neil Gunton
RAND() is slated for improvement. Thanks for any ideas or insights... -Neil Gunton -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Problems with Replication in 4.0.17

2004-01-19 Thread Neil Gunton
Neil Gunton wrote: > > Since I didn't get any replies to my previous message (see below), I am > trying to compile MySQL myself, to see if it results in a more stable > system when using replication. However this is failing consistently with > the following error: > > m

Re: [Fwd: Re: Replication syncronization lag.]

2004-01-15 Thread Neil Gunton
Jonathan Tullett wrote: > > Further to the email below,I performed the upgrade last night and we are > now running mysql 4.0.16. > > the last on the syncronization hasnt reduced any, so if anyone knows how > else I can keep these two databases in sync, I would be very interested > in knowing how!

Re: Problems with Replication in 4.0.17

2004-01-14 Thread Neil Gunton
solutions. Does anyone have the secret incantation to successfully build MySQL 4.0.17? I fully realize that MySQL AB recommends using the binary rpms supplied by them, but since I am having no luck with finding out what's wrong with replication, I think it makes sense to try and build it

Re: loading dates

2004-01-13 Thread Neil Gunton
Antonio De Luna wrote: > > Hi, I've got a csv archive with a date field 15/02/03, how can I load it to a > date field with the mysql date format (ISO ? ) 2003-02-15 ? Well, if you're a Unix type, then you could pipe the input through a small Perl script: #!/usr/bin/perl -w while (<>) {

Problems with Replication in 4.0.17

2004-01-13 Thread Neil Gunton
finally say that I've always been 100% happy with the robustness of MySQL, so this was a little shocking to me! I think MySQL is an extremely useful database system, and I plan to continue using it. Hopefully all this is just an obscure bug. Thanks, -Neil Gunton -- MySQL General Mailing