Re: [PHP-DB] Problem w/ mysql_pconnect

2002-06-24 Thread Tracker 1
Yes, the actual resolution of how the system is accessed is restricted, usually the accounts are restricted by user@localhost, however, you can iirc use user@% for access from anywhere, as part of the grant statement... you can also change the account's host in the mysql.user table. Be carefull

[PHP-DB] Re: Problem w/ mysql_pconnect

2002-06-24 Thread Tracker 1
php, is probably resolving localhost, to its' bound external ip, or something other than 127.0.0.1 (in your hosts file, make sure that localhost is in it.) or change the user's host in the mysql.user table to localhost.localdomain, which will work too. --

[PHP-DB] Re: Question

2002-06-24 Thread Tracker 1
you are thinking backwards.. drives 1- computers tblComputers iCompID As BigInt Primary Key Autonumber, sCompName As VARCHAR(25) ... tblDrives iDriveID As BigInt Primary Key Autonumber, iComputerID As BigInt Not Null, Foreign Key fkDriveComputer (iCompID) References

Re: [PHP-DB] Question

2002-06-24 Thread Tracker 1
in this instance, where a computer isn't likely to contain more than x drives, it may work, however, if he wants to later include sn's, and mfg's a separate table would be better.. :) -- === Michael J. Ryan -

[PHP-DB] Re: Whats more efficient....?

2002-06-24 Thread Tracker 1
For now, probably more effective to run separate queries, in 4.1 mySQL is supposed to include stored proc's at least for InnoDB tables, which would be best of all... and is what I would like to see, in addition to multiple query/recordset returns... in MS-SQL/DB2/Oracle, i've created some

[PHP-DB] Re: sql standard

2002-06-24 Thread Tracker 1
usually, stick with one of the following.. all lowercase, all uppercase, Or Always InterCase or, my personal preference... lblInterCase Have seen some that will make DB names caps, tbl names lower, and column names lblInterCase... pick what you want, and go with it, if you are working with