| 00:01.46 | wps | in PHP, I can test a variable even or odd with %2 |
| 00:02.06 | wps | is there an equivelent for that in javascript? |
| 00:03.47 | fungus | yes. |
| 00:03.53 | fungus | var % 2 |
| 00:04.00 | fungus | https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/Operators/Arithmetic_Operators |
| 00:04.42 | wps | thanks |
| 00:05.26 | wps | doesn't var++; work in javascript? |
| 00:05.31 | wps | to increment it by one? |
| 03:33.40 | *** join/#uphpu beandog (n=sdibb@gentoo/developer/beandog) |
| 03:33.40 | *** mode/#UPHPU [+v beandog] by ChanServ |
| 13:03.19 | *** join/#uphpu SunSparc (n=sparky@71-36-65-45.slkc.qwest.net) |
| 13:03.19 | *** mode/#UPHPU [+v SunSparc] by ChanServ |
| 14:20.33 | carmony | DB Question for anyone on.... on MySQL InnoDB, anyone know any information on when a table is getting too big, aka it has too many rows or its size is to big so it starts loosing performance quickly? |
| 14:21.39 | eggyknap | That happens? |
| 14:22.10 | carmony | I dunno, I've heard rumors :P |
| 14:24.29 | carmony | I got a 7.5GB table with about 150 million rows |
| 14:27.13 | carmony | just wondering if I'm going to run into trouble down the road |
| 14:33.08 | eggyknap | Certainly if you've crummy hardware, poorly built queries or schema, etc. then that will cause problems on a table that large :) |
| 14:38.09 | carmony | hardware isn't a problem |
| 14:38.24 | carmony | terrible schema and horrible queries are somthing I've inherited from day one |
| 14:38.49 | carmony | When I started, the home page required 150+ queries |
| 14:38.59 | eggyknap | In the PostgreSQL world, I'd strongly consider partitioning a table that size, or creating a bunch of partial indexes. Dunno if MySQL lets you do that. |
| 14:39.31 | carmony | I'm thinking paritioning != sharding |
| 14:41.04 | eggyknap | Partitioning is easier. Sharding, as I've seen the term used, means partitioning, and then sticking a partition on a separate server. |
| 14:54.12 | carmony | yeah, youd have like a table_100000 and table_200000 |
| 14:56.05 | eggyknap | Right. But for that to be useful, you need to be able to exclude some/most of the partitions from consideration for a particular query |
| 14:56.30 | eggyknap | Well, in PostgreSQL you'd have separate tables like that. In Oracle, you'd just see partitions of the same table. Not sure about other DBs. |
| 15:05.28 | Dezertol | There are production databases in excess of 7 TB of data. Since 5.0.4, maximum number of rows is 4 billion * 4 billion. Prior to 5.0.4, there was a limitation of 2^32 (4 Billion) rows in a MySQL table. This can be overcome by recompiling MySQL though." |
| 15:05.44 | Dezertol | that's from a mysql rep I was talking to recenly |
| 16:10.34 | *** join/#uphpu mgeary (n=mgeary@69.169.142.45.provo.static.broadweave.net) |
| 16:10.34 | *** mode/#UPHPU [+v mgeary] by ChanServ |
| 16:38.17 | thebigdog | beandog, you around? |
| 17:40.11 | beandog | thebigdog: for a second |
| 17:40.39 | eggyknap | We have beandog, and thebigdog, but I ask you, where are all the cats? |
| 17:41.52 | beandog | heh |
| 17:42.40 | thebigdog | beandog, you heading out? |
| 17:42.57 | beandog | thebigdog: no, just dont wanna be on the puter right now |
| 22:01.35 | herlo | mindjuju: ping |
| 22:06.43 | *** join/#uphpu KirkOuimet (n=chatzill@69.169.132.234.provo.static.broadweave.net) |
| 23:02.56 | *** join/#uphpu mgeary (n=mgeary@69.169.142.45.provo.static.broadweave.net) |
| 23:02.56 | *** mode/#UPHPU [+v mgeary] by ChanServ |
| 23:03.50 | mgeary | ~yow |