vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Very weird problem here. We have an HTML form/PHP script which writes comany listings to a database. Everything was working fine. One of my coworkers who is not in today, setup a new user. This new user can enter listings into the database. The PHP script also has the option to search the database and display the results. The new user can search for the company she just entered and it shows up on the PHP page. However, a search of the database itself doesn't show the company that was just added. I have to do a very specific search for one of the columns before the listing will show up. But it doesn't show up in any "SELECT * FROM table()" or "SELECT * FROM table() WHERE company="company name" statements. I am just wondering if there is some sort of "Hide" option for a row that would cause it not to be a part of a normal query. Or has anyone run into this problem before. I am using MySQL 5. Again, the only query that will find the company, is if you define the specific value in a column called reserved_1. I can look on the PHP form to see what that value is for the company and then search in SQL using "SELECT * FROM table() WHERE reserved_1="some number". That is the only way to find the company in the database. |
| |||
| Jerim79 wrote: > Very weird problem here. We have an HTML form/PHP script which writes > comany listings to a database. Everything was working fine. One of my > coworkers who is not in today, setup a new user. This new user can > enter listings into the database. The PHP script also has the option to > search the database and display the results. The new user can search > for the company she just entered and it shows up on the PHP page. > > However, a search of the database itself doesn't show the company that > was just added. I have to do a very specific search for one of the > columns before the listing will show up. But it doesn't show up in any > "SELECT * FROM table()" or "SELECT * FROM table() WHERE > company="company name" statements. I am just wondering if there is some > sort of "Hide" option for a row that would cause it not to be a part of > a normal query. Or has anyone run into this problem before. I am using > MySQL 5. > > Again, the only query that will find the company, is if you define the > specific value in a column called reserved_1. I can look on the PHP > form to see what that value is for the company and then search in SQL > using "SELECT * FROM table() WHERE reserved_1="some number". That is > the only way to find the company in the database. > No, there isn't any way to "hide" information like this. A SELECT * statement will return all rows in the table. Are you sure you aren't maybe selecting from a view? And have you tried it from a MySQL command line prompt, just to make sure? Also, SELECT * FROM table() is invalid syntax, but I suspect that was just a typo on your part. This one is strange. -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ================== |
| ||||
| >Very weird problem here. We have an HTML form/PHP script which writes >comany listings to a database. Everything was working fine. One of my >coworkers who is not in today, setup a new user. This new user can >enter listings into the database. The PHP script also has the option to >search the database and display the results. The new user can search >for the company she just entered and it shows up on the PHP page. > >However, a search of the database itself doesn't show the company that >was just added. I have to do a very specific search for one of the >columns before the listing will show up. But it doesn't show up in any >"SELECT * FROM table()" or "SELECT * FROM table() WHERE >company="company name" statements. I am just wondering if there is some >sort of "Hide" option for a row that would cause it not to be a part of >a normal query. Or has anyone run into this problem before. I am using >MySQL 5. Could this be an issue of the connection that inserted the data can see an as-yet-uncommitted transaction but the others can't, because it isn't committed yet? |