Posted by Jerry Stuckle on 10/22/07 02:25

The Natural Philosopher wrote:
> Jerry Stuckle wrote:
>> Richard Brooks wrote:
>>> Jerry Stuckle said the following on 20/10/2007 14:22:
>>>> Richard Brooks wrote:
>>>>> Does anyone here open a second MySQL database and use that as a
>>>>> straight IDX type file that points to the record number in the main
>>>>> database, for speed's sake?
>>>>>
>>>>> Some time ago I'd set up a standard php login routine and hit a
>>>>> brick wall as then found out that my host didn't allow external
>>>>> login's (at that time) with MySQL (true!) so I got around it by
>>>>> writing a random access database with separate IDX files for
>>>>> username and passwords for cross-referencing.
>>>>>
>>>>> Things have all changed and the php/MySQL setup is as standard, so
>>>>> I have to rewrite the checking routines which leaves me to wonder
>>>>> if others use a second MySQL database as an Index file for any
>>>>> reason or is it all fast enough using one database?
>>>>>
>>>>> Or even, is there any point changing at all?
>>>>>
>>>>> Many thanks,
>>>>>
>>>>>
>>>>> Richard.
>>>>>
>>>>
>>>> And what does this have to do with PHP? If you want a good answer
>>>> about MySQL, try a MySQL newsgroup - such as comp.databases.mysql.
>>>> That's where the MySQL experts hang out, not here.
>>>
>>> Well, I've got my whole system written in MySQL-less PHP! Would that
>>> help? And I would not believe that php'ers never even think of
>>> dabbling in MySQL.
>>>
>>>
>>
>> First of all, you didn't say that.
>>
>> However, you're asking how to best structure MySQL files, not how to
>> program in PHP. For MySQL questions, I recommend a MySQL newsgroup.
>>
> Why? because you have less of a clue about MySQL than PHP?
>

Because this is a PHP newsgroup, stoopid. But you don't seem to
understand the difference.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]