Search results for query: *

The commas should follow the column names when using the CREATE statement, not precede them. Also, you might want to think about lengthening the URL column's data type as shown below. create table enterprise_programming ( Submitter VARCHAR(20), URL VARCHAR(255)...

You have spaces in your field names. It's not advisable to create field names with spaces. I believe you can still do it by using single quotes around the field names containing spaces, but it's not considered good practice. You'll want to stay away from using special characters as well.

Is it a particular field in the database that doesn't like the string? I would check the data type of the field you're trying to update and the data type of the variable you're trying to pass. Sometimes you can run into situation where a Unicode-formatted or ANSI-formatted string won't work...

No, that was one of the first things I checked

Yeah, I tried that. I used the following code to print out all the column names for the 'stories' table and sure enough the 'pub_year' column' is not showing up, even though it's there. I gotta feeling it's something on the hosting provider's end. It just doesn't make sense. It's like there's...

The following code works perfectly on our test box, but not on the live box. The page doesn't recognize the new 'pub_year' column even though it is there and can be queried on from phpMyAdmin. $sql1 = "SELECT * FROM stories WHERE page = 'legEX Archive' AND published IS NOT NULL ORDER BY...

Thanks, I thought your suggestion might do the trick, so I changed the column names to 'pub_year' and 'pub_month' and the page still will not return the new column names. It's like the data is being cached or something.

I recently add two new columns (month & year) to a table in our test database for a client. I wrote some PHP code to query the new columns and everything worked fine. I then made the exact same changes to our production database which uses the phpMyAdmin web interface at our hosting provider. It...