Re: incorrect api docs

2002-10-27 Thread Nathan Neulinger
Last try, if this doesn't go through, screw it. 

On Sun, 2002-10-27 at 21:31, [EMAIL PROTECTED] wrote:
 Your message cannot be posted because it appears to be either spam or
 simply off topic to our filter. To bypass the filter you must include
 one of the following words in your message:
 
 sql,query
 
 If you just reply to this message, and include the entire text of it in the
 reply, your reply will go through. However, you should
 first review the text of the message to make sure it has something to do
 with MySQL. Just typing the word MySQL once will be sufficient, for example.
 
 You have written the following:
 
 Have not verified recently, other than when I grabbed one of the version
 4 binary tarballs, but API docs for the open db (whatever it's called, 
 don't have using code in front of me at the moment) call seem to 
 indicate that you can specify 0 for the port number and it will use the 
 default port number. This does not appear to be the case, it tries to 
 bind to port 0 in that case. (On linux, have not tried elsewhere.)
 
 I think the api documented behavior would definately be preferable.
 
 (BTW - Y'all make it far too much a pita to submit a bug report.)
 
 -- Nathan
 
 
 Nathan Neulinger   EMail:  [EMAIL PROTECTED]
 University of Missouri - Rolla Phone: (573) 341-4841
 Computing Services   Fax: (573) 341-4216
-- 


Nathan Neulinger   EMail:  [EMAIL PROTECTED]
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services   Fax: (573) 341-4216


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




explain on merge table versus underlying table:

2001-03-26 Thread Nathan Neulinger


Note the difference:

mysql explain select * from syslogs_main where
host='openview.cc.umr.edu' and msg like '%IPACCESS%';
+--+--+---++-+---+---++
| table| type | possible_keys | key| key_len | ref   | rows 
| Extra  |
+--+--+---++-+---+---++
| syslogs_main | ref  | sl_hsp| sl_hsp |  50 | const | 20487
| where used |
+--+--+---++-+---+---++
1 row in set (0.00 sec)

mysql explain select * from syslogs where host='openview.cc.umr.edu'
and msg like '%IPACCESS%';
+-+--+---+--+-+--+++
| table   | type | possible_keys | key  | key_len | ref  | rows   |
Extra  |
+-+--+---+--+-+--+++
| syslogs | ALL  | NULL  | NULL |NULL | NULL | 754049 |
where used |
+-+--+---+--+-+--+++
1 row in set (0.57 sec)


Syslogs is a merge table over syslogs_main (and several others).

Appears the output is wrong, cause the queries take about the same time.

I'm not sure if it would be the ideal approach, but I'd be happy with
explain on a merge table generating a row in the response for each table
in the merge. ie:

++--+---++-+---+---++
| table  | type | possible_keys | key| key_len | ref   |
rows  | Extra  |
++--+---++-+---+---++
| syslogs_main   | ref  | sl_hsp| sl_hsp |  50 | const |
20487 | where used |
| syslogs_mail   | ref  | sl_hsp| sl_hsp |  50 | const |
20487 | where used |
| syslogs_dhcp   | ref  | sl_hsp| sl_hsp |  50 | const |
20487 | where used |
| syslogs_mredir | ref  | sl_hsp| sl_hsp |  50 | const |
20487 | where used |
++--+---++-+---+---++



-- Nathan


Nathan Neulinger   EMail:  [EMAIL PROTECTED]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems ProgrammingFax: (573) 341-4216

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php





request - insert into merge tables

2001-03-12 Thread Nathan Neulinger

Seems like it would be relatively easy to implement inserting into merge
tables. I'd like to be able to at an absolute minimum round-robin
insert, but even better would be something like you can do with
partitioning in oracle.

Baically, something like this:

create table x (...) type=merge union=(a,b,c,d) 
partition=a:(where key=val1) partition=b:(where keyval2 and keyval3);

if an insert attempt is made to that can't be partitioned, an error
should be generated, otherwise, it should fall back. In the above
example, it would also round-robin between c,d wherever no partition
criteria didn't match. Whether or not multiple matching partition
criteria should also round-robin is another good question.

It's just an idea, might make merge tables quite a bit more powerful.

-- Nathan


Nathan Neulinger   EMail:  [EMAIL PROTECTED]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems ProgrammingFax: (573) 341-4216

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php