| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Comments:
<Eldritch> 0
<dravine> well
<dravine> in their defense, the topic is Kill your parents Kill your parents Kill your parents then Kill yourself
<Eldritch> -4
<p`u> -4 = -4
<Sean|> -5
<p`u> -5 = -5
<Eldritch> -99999999999999999999
<p`u> -99999999999999999999 = -99999999999999999999
<dravine> whatup tasm
<Eldritch> kill it!
<dravine> :D
<_TaSm> Nadda, just work.
<dravine> right on
<Eldritch> -9999999999 * -99999999999999999999999999999999999999999999
<p`u> -9999999999 * -99999999999999999999999999999999999999999999 = 999999999899999999999999999999999999999999990000000001
<_TaSm> Accually, got a neat freelance gig I'm helping my friend with.
<Eldritch> whos ****e head bot is that?
<dravine> mine
<Eldritch> explains it.
<dravine> he's actually pretty handy
<dravine> .head www.google.com
<p`u> 200 OK
<p`u> Server: GWS/2.1
<Eldritch> 1 +1
<p`u> 1 +1 = 2
<Eldritch> yeah i could of never worked it out myself
<dravine> .google secure php forum
<p`u> About 539000 results. Displaying 1 - 5
<_TaSm> One part of the DB schema I'm havin a tricky time with gotta figure out the best way to handle it.
<p`u> 1. http://forums.devnetwork.net/index.php (PHP Developer's Network Forums)
<p`u> 2. http://codewalkers.com/ (codewalkers.com - main page - PHP Help)
<p`u> 3. http://www.astaro.org/ (Astaro User Bulletin Board: Viewing list of forums)
<p`u> 4. http://www.sitepoint.com/article/php-security-blunders (Top 7 PHP Security Blunders [PHP & MySQL Tutorials])
<p`u> 5. http://www.phpsecure.info/ (phpSecure.info - Welcome .. script, patch, faille, hack, news ...)
<|pit> the **** p`u
<_TaSm> !****
<_TaSm> !**** frag
<dravine> _TaSm, db schema for what?
<_TaSm> !frag
<p`u> MAN THE POOP DECK
<|pit> eh tasm
<Eldritch> pi * 99
<|pit> !frag frag
<p`u> MAN THE POOP DECK
<dravine> .quote
<p`u> <jperez> my last babe told me mine was ridiculous contrary to his old friend's one
<_TaSm> Well I've got "items" and I've got "results" for each "item"
<|pit> !frag
<p`u> MAN THE POOP DECK
<|pit> oh right
<|pit> who's bot is it?
<dravine> mine
<|pit> ahhh
<dravine> well a friend of mines, but I brought it in
<dravine> his .ro fu is powerful
<dravine> observe
<Tamahome> ooo, that security blunders page is good
<_TaSm> Here is the tricky thing. There will only be 12 items, however, each item will have multiple results. BUT the result info changes per item.
<|pit> ohhhh nice
<dravine> so if you sick him on a ro, man it's hours of fun
<dravine> .host www.msn.com
<p`u> error while resolving: lookup timed out
<|pit> you should make him quote random stuff
<dravine> .quote dravine
<p`u> <dravine:#apache> stupid frenchie
<|pit> random annoying stuff
<dravine> .quote dravine
<Sean|> .quite Sean|
<Sean|> .quote Sean|
<Sean|> gay
<p`u> <dravine> hah, azers slut girlfriend fisted his ***
<p`u> no quotes found
<dravine> .quote dravine
<p`u> <dravine> I like it (PHP) because it's similar to C enough to where I can write the code without really having to think about it.
<dravine> .quote dravine midgets
<p`u> not enough data
<dravine> .quote midgets
<p`u> no quotes found
<dravine> hrm
<dravine> can't remember how to do that
<M0tH3r[x]> .die
<dravine> .quote dravine |midgets|
<p`u> not enough data
<dravine> .quote dravine /midgets/
<_TaSm> So the three ideas I've come up with are 1) seperate tables for each item... 2) A table with lots of generic columns and define the colums in a rank_desc table... OR 3) Create a rank_desc table and then have a results table with only three columns, item_id, rank_desc_id, rank
<p`u> <dravine> ************** NEW! AMAZING! Magazine fed toothless parapalegice *** midgets with 2 handles and vibrating butt plugs ***** Your's for only 69 easy payments of $6.99
<_TaSm> The prob is none of the three is an ideal solution.
<_TaSm> .part
<_TaSm> .shaddup
<_TaSm> .****
<Tamahome> how do you generate .htp***wd files for Apache?
<_TaSm> Tamahome #apache ?
<dravine> _TaSm, he's set to quiet mode
<Tamahome> oh there's a channel for that? kewl
<dravine> should only say stuff when spoken too
<_TaSm> Oh I dont really care dravine, I just want an answer to my prediciment. ;)
<_TaSm> Lemme repeat
<dravine> _TaSm, you might be over complicating it
<_TaSm> Here is the tricky thing. There will only be 12 items, however, each item will have multiple results. BUT the result info changes per item.
<_TaSm> So the three ideas I've come up with are 1) seperate tables for each item... 2) A table with lots of generic columns and define the colums in a rank_desc table... OR 3) Create a rank_desc table and then have a results table with only three columns, item_id, rank_desc_id, rank
<dravine> what type of relationship does the table structure require
<_TaSm> Its basically a many to one.
<_TaSm> The only problem is, the many changes depending on what the one is.
<dravine> I'd use a linking table
<_TaSm> Ie, item1 might have three peices of result data.
<dravine> the 3 fields thing
<_TaSm> Ya thats waht I'm leaning towards.
<_TaSm> Only prob with that is, we're talking 50mill+ rows.
<Tamahome> daaaaamn
<dravine> just properly index it, and you should be set
<Tamahome> that's some table.
<_TaSm> The table isn't complex, its just lots of data.
<dravine> postgres?
<_TaSm> Ya, I'm thinkin it should still be fast.
<Tamahome> is rank_desc a field name, or some kind of aggregate function?
<_TaSm> rank_desc is a table that woudl define the rank types per item.
<_TaSm> Ie rank_desc would provide how many "bits" of rank data there should be for each item.
<_TaSm> The nice thing is if I do it that way, it'll be totally relational, and I'll be able to add items w/o adding programming.
<_TaSm> In the first option, having seperate tables, that woudl require additonal programming depending on how many items there were and on how much rank data they were based.
<dravine> well, that's an important cabability
<_TaSm> Ya, it means, "Program Once"
<dravine> _TaSm, as a rule of thumb, I generally try to make things expandable with minimal changes to the application code
<_TaSm> But lots of rows of data.
<_TaSm> I guess it'll just be an interesting test of the db.
<dravine> what db?
<Toka> is it ok to use $var = function($var); ??
<Toka> or should I use another variable for return value?
<archaevs> Toka, that's ok
<Toka> thanks
<_TaSm> Oh, not sure, it'll probally be either mysql or postrgres.
<dravine> well
<dravine> if you use postgres, you can use stored procedures for fetching the linked table data
<dravine> which should be very fast
<_TaSm> I'm going to have to create temp tables too.
<_TaSm> To do sorting, etc.
<_TaSm> Because there wont be a "real" table.
<dravine> ?
<dravine> why do you need temp tables?
<_TaSm> Because each rank has multiple items, in order to sort by item you'd need to create a temp table from which to sort on.
<dravine> http://www.postgresql.org/docs/current/static/tutorial-views.html
<dravine> oh contraire
<p`u> That URL would be better as http://w.ick.ca/4878
<Everything> Why might a variable that outputs a value decide it won't output the samw value when you use the date function?
<irzyxel> variables dont output anything
Return to
#php
or
Go to some related
logs:
#c
bruneta30
#linux
run programs on ios
#MissKitten
#linuxhelp
What bowling term means three straight strikes?
#networking
#MissKitten
yy2bggggs
|
|
