php/MySQL index filing?

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.

Re: php/MySQL index filing?

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.

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

Re: php/MySQL index filing?

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.

Re: php/MySQL index filing?

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.

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

Re: php/MySQL index filing?

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?

Re: php/MySQL index filing?

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
==================

Re: php/MySQL index filing?

Jerry Stuckle said the following on 21/10/2007 19:21:
> 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.

Okay! BTW, you'd better tell bill not to talk about MySQL TimeZone
support or just sing to yourself with fingers in your ears and there's
no use saying that it doesn't count as both this and his post includes
php usage.

I already have a php ONLY database setup with php IDX type flatfiles
with a file offset pointer in them. It was hard work but it does work.


[1]. Is there a point changing it over to that other type of database
(using php of course)?
[2]. If there is anyone using databases in php, do they use a main and
IDX files separately?
[3]. Using php, did your mother breast feed you at all?

Re: php/MySQL index filing?

Richard Brooks wrote:
> Jerry Stuckle said the following on 21/10/2007 19:21:
>> 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.
>
> Okay! BTW, you'd better tell bill not to talk about MySQL TimeZone
> support or just sing to yourself with fingers in your ears and there's
> no use saying that it doesn't count as both this and his post includes
> php usage.
>
> I already have a php ONLY database setup with php IDX type flatfiles
> with a file offset pointer in them. It was hard work but it does work.
>
>
> [1]. Is there a point changing it over to that other type of database
> (using php of course)?

Check in the newsgroups for the database(s) you're trying to use.
That's where database experts hang out.

> [2]. If there is anyone using databases in php, do they use a main and
> IDX files separately?

There are lots of people using databases in PHP. As for maintaining
separate files, ask in the newsgroups for the database(s) you're trying
to use. That's where database experts hang out.

> [3]. Using php, did your mother breast feed you at all?
>

Sheesh. Try to give someone some help and they insult you.

What are you, a troll? You're asking about databases. Databases are
language neutral - they are used with a number of languages. But
obviously you don't understand that. So you need to go to a database
newsgroup to learn about it.


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

Re: php/MySQL index filing?

Jerry Stuckle wrote:
> Richard Brooks wrote:

>
>> [3]. Using php, did your mother breast feed you at all?
>>
>
> Sheesh. Try to give someone some help and they insult you.
>
> What are you, a troll?

Everyone's a troll who disagrees with you, Jerry.

Re: php/MySQL index filing?

The Natural Philosopher wrote:
> Jerry Stuckle wrote:
>> Richard Brooks wrote:
>
>>
>>> [3]. Using php, did your mother breast feed you at all?
>>>
>>
>> Sheesh. Try to give someone some help and they insult you.
>>
>> What are you, a troll?
>
> Everyone's a troll who disagrees with you, Jerry.
>

No, just assholes like you.

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

Re: php/MySQL index filing?

Jerry Stuckle said the following on 22/10/2007 12:15:

> Sheesh. Try to give someone some help and they insult you.

Sorry! I was busy reading all the stuff that comes up in Google with
"Jerry Stuckle Asshole" as the keyword phrase.

> What are you, a troll? You're asking about databases. Databases are
> language neutral - they are used with a number of languages. But
> obviously you don't understand that. So you need to go to a database
> newsgroup to learn about it.

But using them within a php environment is the important part and as php
is the language (okay, it's good old C really) being used and people who
have written them would be lurking around here, they would know of any
pitfalls in using a 'roll your own' method.

Now, go outside and play if the other parents will let you play with
their children. It'll do you some good to get a bloody nose and have
your lunch money stolen sometimes.

Re: php/MySQL index filing?

Richard Brooks wrote:
> Jerry Stuckle said the following on 22/10/2007 12:15:
>
>> Sheesh. Try to give someone some help and they insult you.
>
> Sorry! I was busy reading all the stuff that comes up in Google with
> "Jerry Stuckle Asshole" as the keyword phrase.
>
>> What are you, a troll? You're asking about databases. Databases are
>> language neutral - they are used with a number of languages. But
>> obviously you don't understand that. So you need to go to a database
>> newsgroup to learn about it.
>
> But using them within a php environment is the important part and as php
> is the language (okay, it's good old C really) being used and people who
> have written them would be lurking around here, they would know of any
> pitfalls in using a 'roll your own' method.
>
> Now, go outside and play if the other parents will let you play with
> their children. It'll do you some good to get a bloody nose and have
> your lunch money stolen sometimes.
>
>

First of all, it's not "Good Old C". This is PHP.

Second of all, you obviously have no understanding of how RDB's work. I
assumed since you "wrote your own database" you would at least have
*SOME* inkling how they work. But obviously you have *none*.

And no, most people in this group are smarter than to try to "roll your
own". Obviously you're not that smart.

I tried to give you some good advice. You came back with insults.

Here's one more try. Learn how *REAL* databases work. Then come back
when you can ask *intelligent* questions.

Or learn to take good advice.

And by the way - sure, you can find some negative things about me.
That's because I don't put up with assholes like you. And I'm not
afraid to tell you that.

Now, you're mommy's calling. Better go see what she wants.

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

Re: php/MySQL index filing?

Jerry Stuckle said the following on 23/10/2007 14:10:
> Richard Brooks wrote:
>> Jerry Stuckle said the following on 22/10/2007 12:15:
>>
>>> Sheesh. Try to give someone some help and they insult you.
>>
>> Sorry! I was busy reading all the stuff that comes up in Google with
>> "Jerry Stuckle Asshole" as the keyword phrase.
>>
>>> What are you, a troll? You're asking about databases. Databases are
>>> language neutral - they are used with a number of languages. But
>>> obviously you don't understand that. So you need to go to a database
>>> newsgroup to learn about it.
>>
>> But using them within a php environment is the important part and as
>> php is the language (okay, it's good old C really) being used and
>> people who have written them would be lurking around here, they would
>> know of any pitfalls in using a 'roll your own' method.
>>
>> Now, go outside and play if the other parents will let you play with
>> their children. It'll do you some good to get a bloody nose and have
>> your lunch money stolen sometimes.
>>
>>
>
> First of all, it's not "Good Old C". This is PHP.

History

PHP was written as a set of Common Gateway Interface (CGI) binaries in
the C programming language by the Danish/Greenlandic programmer Rasmus
Lerdorf in 1994, to replace a small set of Perl scripts he had been
using to maintain his personal homepage.[3] Lerdorf initially created
PHP to display his résumé and to collect certain data, such as how much
traffic his page was receiving. Personal Home Page Tools was publicly
released on 8 June 1995 after Lerdorf combined it with his own Form
Interpreter to create PHP/FI (this release is considered PHP version 2).[4]

> Second of all, you obviously have no understanding of how RDB's work. I
> assumed since you "wrote your own database" you would at least have
> *SOME* inkling how they work. But obviously you have *none*.
>
> And no, most people in this group are smarter than to try to "roll your
> own". Obviously you're not that smart.

Onideus, is that you?

Re: php/MySQL index filing?

Richard Brooks wrote:
> Jerry Stuckle said the following on 23/10/2007 14:10:
>> Richard Brooks wrote:
>>> Jerry Stuckle said the following on 22/10/2007 12:15:
>>>
>>>> Sheesh. Try to give someone some help and they insult you.
>>>
>>> Sorry! I was busy reading all the stuff that comes up in Google with
>>> "Jerry Stuckle Asshole" as the keyword phrase.
>>>
>>>> What are you, a troll? You're asking about databases. Databases
>>>> are language neutral - they are used with a number of languages.
>>>> But obviously you don't understand that. So you need to go to a
>>>> database newsgroup to learn about it.
>>>
>>> But using them within a php environment is the important part and as
>>> php is the language (okay, it's good old C really) being used and
>>> people who have written them would be lurking around here, they would
>>> know of any pitfalls in using a 'roll your own' method.
>>>
>>> Now, go outside and play if the other parents will let you play with
>>> their children. It'll do you some good to get a bloody nose and have
>>> your lunch money stolen sometimes.
>>>
>>>
>>
>> First of all, it's not "Good Old C". This is PHP.
>
> History
>
> PHP was written as a set of Common Gateway Interface (CGI) binaries in
> the C programming language by the Danish/Greenlandic programmer Rasmus
> Lerdorf in 1994, to replace a small set of Perl scripts he had been
> using to maintain his personal homepage.[3] Lerdorf initially created
> PHP to display his résumé and to collect certain data, such as how much
> traffic his page was receiving. Personal Home Page Tools was publicly
> released on 8 June 1995 after Lerdorf combined it with his own Form
> Interpreter to create PHP/FI (this release is considered PHP version 2).[4]
>

So? Linux was basically written in C. That doesn't make it essentially
a C programming language. And the same can be said for most of Windows.

Come to think of it, I think most of VBScript.NET is written in C. Does
that make it basically a C language, also? How about Excel? Or Open
Office?

Just because something was written in C doesn't mean it is basically C.


>> Second of all, you obviously have no understanding of how RDB's work.
>> I assumed since you "wrote your own database" you would at least have
>> *SOME* inkling how they work. But obviously you have *none*.
>>
>> And no, most people in this group are smarter than to try to "roll
>> your own". Obviously you're not that smart.
>
> Onideus, is that you?
>


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