August, 2007: Hmmm, a ticket aggregator, huh? Yeah, I can throw that together in a month over the summer. Then we can find another idea so I can work on

August, 2007: Hmmm, a ticket aggregator, huh? Yeah, I can throw that together in a month over the summer. Then we can find another idea so I can work on something *hard*! July, 2009: Fuck, I'm *still* working on this thing?! When did it turn into a fully-fledged, funded company? And why can't I find an intern to help me with all this damn work?! The original plan for TicketStumbler was a quick, stop-gap solution to the problem of not having jobs anymore. It was supposed to take a couple months, at most. Some day I might get into why it will soon have taken a year and 3 complete re-designs (working on #3 as I type!) and 3 re-writes of a high-performance site crawler / parser which is now largely obsolete thanks to proper APIs, just to get to a point where we kinda know what the hell we're doing. Until then, I just laugh at Techcrunch commenters who think they can clone it in a weekend. But I can get you started: CREATE TABLE ticket_ticket ( id serial NOT NULL, event_id integer NOT NULL, section character varying(150) NOT NULL, "row" character varying(150) NOT NULL, price numeric(9,2) NOT NULL, quantity smallint NOT NULL, url character varying(300) NOT NULL, extra text, broker_id integer NOT NULL, last_update timestamp with time zone NOT NULL, root_url character varying(300), CONSTRAINT ticket_ticket_pkey PRIMARY KEY (id), CONSTRAINT broker_id_refs_id_2b5e6c11effcebee FOREIGN KEY (broker_id) REFERENCES review_broker (id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION DEFERRABLE INITIALLY DEFERRED, CONSTRAINT ticket_ticket_quantity_check CHECK (quantity >= 0) ) WITH (OIDS=FALSE); Good luck! :D