My only complaints have 0 to do with the layout. I happen to like it, BTW.
What pisses me off? Having to click "show full article" and "show all comments" EVERY TIME I VISIT. Cookies, motherf***er! Do you use them?? ;)
My only complaints have 0 to do with the layout. I happen to like it, BTW.
What pisses me off? Having to click "show full article" and "show all comments" EVERY TIME I VISIT. Cookies, motherf***er! Do you use them?? ;)
Why not just use an existing framework, like Symfony or CakePHP? No need to reinvent the wheel.
Proof that XML is the solution to every problem!
http://www.informationweek.com/showArticle.jhtml;jsessionid=R2FGBWGYKLN5OQSNDLPCKH0CJUNN2JVN?articleID=197700815&queryText=xml
That's up there with the job in Portland, OR that wants "5-7 years of C#/ASP.NET." Neat trick, considering C# didn't launch until 2002. I can just see the interview:
"Sorry, you don't meet our requirements. We require 5-7 years of C#/ASP.NET experience."
"Oh, sorry, here I'll hop into my time machine, go back to 2002, and re-live the last 4 years so I can get the experience you want."
"..."
"OK, I'm back. Here let me fix that resume..."
Nathan
Thanks for your input.
I'm really not looking to create address templates for every single country; basically I'm creating US-style address forms for US & Canada, and letting everyone else just enter their addresses on up to 5 blank lines (with the 6th automatically being filled with the country name).
But you're right--it's a 1-to-1 relationship, it's unnecessary; thinking too much like a programmer. :) =
Nathan
I've hit a bit of a brick wall. I'm developing a PHP script to walk a user through entering a vacation home listing; I've got it 99% working the way I want it to. Where I've hit the wall is getting the data actually written to the database.
MySQL version is 4.0.23 and PHP version is 4.3.10.
I may have overengineered things a bit; addresses are broken into 2 (well, technically three) tables; one for general information that is common to all addressses (geographical area, country, city) and then a table for the US-centric address details (state, zip) and one to handle international addresses.
The trick is how to link the two together.
Here are the table definitions:
address (
address_id INT(10) UNSIGNED DEFAULT '0' NOT NULL AUTO_INCREMENT,
owner SMALLINT(5) UNSIGNED DEFAULT '0', // references site user
type TINYINT(1) UNSIGNED DEFAULT '0' NOT NULL,
continent TINYINT(2) UNSIGNED DEFAULT '0', // continent, country, and region cross-reference other tables.
country SMALLINT(5) DEFAULT '0' NOT NULL,
region SMALLINT(5) DEFAULT '0' NOT NULL,
city VARCHAR(50) DEFAULT '' NOT NULL,
us_address INT(10) DEFAULT '0' NOT NULL, // supposed to reference us-specific address components
intl_address INT(10) DEFAULT '0' NOT NULL, // for everyone else; a given address will use one or the other.
PRIMARY KEY (address_id)
)
us_address (
us_address_id INT(10) UNSIGNED DEFAULT '0' NOT NULL AUTO_INCREMENT,
owner SMALLINT(5) UNSIGNED DEFAULT '0',
box INT(10) UNSIGNED DEFAULT '0' NOT NULL,
street VARCHAR(255) DEFAULT '' NOT NULL,
zip VARCHAR(20) DEFAULT '' NOT NULL,
PRIMARY KEY (us_address_id)
);
So, my question: how do I create entries in these tables simultaneously and reference one from the other? The SQL reference doesn't seem to give me away of finding out "hey, that INSERT statement created record FOO" so I can use it for the other table. And since users can have multiple listings, I need to make sure the tables are consistent.
So, am I overengineering it and should I just dump all the data into the main table, or is there a way to do what I want that I'm missing?
Thanks,
Nathan
Not quite as large a jump as Microsoft did from 3.1 to 95 (or 98 to 2000), but still WTFey: