php/mysql query insert values into enters the records in reverse order
This is a discussion on php/mysql query insert values into enters the records in reverse order within the MySQL forums, part of the Database Server Software category; --> On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> wrote: >Techie Guy wrote: > >> >> Yes I ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-28-2008, 07:06 AM
| ||||
| ||||
 Re: php/mysql query insert values into enters the records in reverse order On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> wrote: >Techie Guy wrote: > >> >> Yes I read the post and clearly understand that it doesn't matter >> generally, what order data is entered into most databases. >> >> However in this case there are over 5000 records already in the >> correct order in the database and it would be nice to keep them that > >May be you *read* the posting, but then you refuse to *understand*. >THERE IS NO ORDER in a MySQL database. > >> way. > >Since there is no order, you can't keep it. Oh but yes you can Existing database contents over 5000 records order by ID DESC ID, REF, field3, field4, field5 5067, IN005067, data3, data4, data5 5066, IN005066, data3, data4, data5 5065, IN005065, data3, data4, data5 5064, IN005064, data3, data4, data5 n 1, IN000001, data3, data4, data5 Txt file contents with no ID field IN005071, data3, data4, data5 IN005070, data3, data4, data5 IN005069, data3, data4, data5 IN005068, data3, data4, data5 Database after contents of txt file written by script ID and REF no longer correspond so when you query ID 5071 REF IN005068 is returned as the record ID, REF, field3, field4, field5 5071, IN005068, data3, data4, data5 5070, IN005069, data3, data4, data5 5069, IN005070, data3, data4, data5 5068, IN005071, data3, data4, data5 5067, IN005067, data3, data4, data5 5066, IN005066, data3, data4, data5 5065, IN005065, data3, data4, data5 5064, IN005064, data3, data4, data5 n 1, IN000001, data3, data4, data5 However if data was entered in reverse order from the txt file. the data would look like this ID, REF, field3, field4, field5 5071, IN005071, data3, data4, data5 5070, IN005070, data3, data4, data5 5069, IN005069, data3, data4, data5 5068, IN005068, data3, data4, data5 5067, IN005067, data3, data4, data5 5066, IN005066, data3, data4, data5 5065, IN005065, data3, data4, data5 5064, IN005064, data3, data4, data5 n 1, IN000001, data3, data4, data5 If you now query ID 5071 it returns REF IN005071 Therefore the order the data is written affect results of previously written scripts      |
|
02-28-2008, 07:06 AM
| |||
| |||
| Re: php/mysql query insert values into enters the records in reverse order On Tue, 01 Nov 2005 18:49:01 +0000, Techie Guy <out@thepub.com> wrote: >On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> >wrote: > >>Techie Guy wrote: >> >>> >>> Yes I read the post and clearly understand that it doesn't matter >>> generally, what order data is entered into most databases. >>> >>> However in this case there are over 5000 records already in the >>> correct order in the database and it would be nice to keep them that >> >>May be you *read* the posting, but then you refuse to *understand*. >>THERE IS NO ORDER in a MySQL database. >> >>> way. >> >>Since there is no order, you can't keep it. > >Oh but yes you can Whatever. -- gburnore at DataBasix dot Com --------------------------------------------------------------------------- How you look depends on where you go. --------------------------------------------------------------------------- Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³ Black Helicopter Repair Services, Ltd.| Official Proof of Purchase ================================================== ========================= |
|
02-28-2008, 07:06 AM
| |||
| |||
| Re: php/mysql query insert values into enters the records in reverseorder Techie Guy wrote: > On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> > wrote: > > >>Techie Guy wrote: >> >> >>>Yes I read the post and clearly understand that it doesn't matter >>>generally, what order data is entered into most databases. >>> >>>However in this case there are over 5000 records already in the >>>correct order in the database and it would be nice to keep them that >> >>May be you *read* the posting, but then you refuse to *understand*. >>THERE IS NO ORDER in a MySQL database. >> >> >>>way. >> >>Since there is no order, you can't keep it. > > > Oh but yes you can > > Existing database contents over 5000 records order by ID DESC > Are you really so dense? This is NOT something inherent in the database. It's only the OUTPUT that's ordered. Hell. > Therefore the order the data is written affect results of previously > written scripts Nonsense. |
|
02-28-2008, 07:06 AM
| |||
| |||
| Re: php/mysql query insert values into enters the records in reverse order On Wed, 02 Nov 2005 00:13:17 +0100, Christian Kirsch <ck@bru6.de> wrote: >Techie Guy wrote: >> On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> >> wrote: >> >> >>>Techie Guy wrote: >>> >>> >>>>Yes I read the post and clearly understand that it doesn't matter >>>>generally, what order data is entered into most databases. >>>> >>>>However in this case there are over 5000 records already in the >>>>correct order in the database and it would be nice to keep them that >>> >>>May be you *read* the posting, but then you refuse to *understand*. >>>THERE IS NO ORDER in a MySQL database. >>> >>> >>>>way. >>> >>>Since there is no order, you can't keep it. >> >> >> Oh but yes you can >> >> Existing database contents over 5000 records order by ID DESC >> > >Are you really so dense? This is NOT something inherent in the database. >It's only the OUTPUT that's ordered. Hell. Yeah. He is. Best to just give up, I'm afraid. > >> Therefore the order the data is written affect results of previously >> written scripts > >Nonsense. Of course it is. I'm wondering why he doesn't just put his text in a flat file and cat it. -- gburnore at DataBasix dot Com --------------------------------------------------------------------------- How you look depends on where you go. --------------------------------------------------------------------------- Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³ Black Helicopter Repair Services, Ltd.| Official Proof of Purchase ================================================== ========================= |
|
02-28-2008, 07:06 AM
| |||
| |||
| Re: php/mysql query insert values into enters the records in reverse order In message <h03fm1t7lfo1v7c2gi320039r6ltigo4su@4ax.com>, Techie Guy <out@thepub.com> writes >>It does. But you apparently didn't read what Steve wrote. It >>shouldn't matter what order they're inserted. > >Yes I read the post and clearly understand that it doesn't matter >generally, what order data is entered into most databases. > >However in this case there are over 5000 records already in the correct >order in the database and it would be nice to keep them that way. >Certain fields also correspond numerically to the ID field and I was >aiming for neatness. The ref# field for example is alphanumeric >IN000000 and the numeric part happens to be the same # as the ID >Entering the txt file in the correct order keeps these fields in line >with the ID #. In general it's a bad idea to build a system that relies on a feature that you don't have direct control of. You are unlikely to have complete control of the sequence of records in a MySQL database because in a compliant relational database the sequence is undefined. You would have no cause for complaint if the next version of MySQL started returning records in some other order. If you want records in a specific order you should always specify it. So my advice is to accept the current behaviour which will break the apparent link between the ref# and the ID. Breaking that linkage is IMHO a good thing. It's probably going to break at some point in the future, best to get it over with. When I had to do something similar I carefully scrambled the sequence of ID numbers so that it was impossible to guess the sequence. Having some apparent relationship between the numbers encourages people to assume that this is always going to be so, and that isn't guaranteed. That assumption will bite you if you allow it to continue. However if you aren't convinced by this then you should be able to sort your text file in reverse order before loading it. Even Windows has a sort command. -- Bernard Peek London, UK. DBA, Manager, Trainer & Author. |
|
02-28-2008, 07:06 AM
| |||
| |||
| Re: php/mysql query insert values into enters the records in reverse order On Wed, 02 Nov 2005 00:13:17 +0100, Christian Kirsch <ck@bru6.de> wrote: >Techie Guy wrote: >> On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> >> wrote: >> >> >>>Techie Guy wrote: >>> >>> >>>>Yes I read the post and clearly understand that it doesn't matter >>>>generally, what order data is entered into most databases. >>>> >>>>However in this case there are over 5000 records already in the >>>>correct order in the database and it would be nice to keep them that >>> >>>May be you *read* the posting, but then you refuse to *understand*. >>>THERE IS NO ORDER in a MySQL database. >>> >>> >>>>way. >>> >>>Since there is no order, you can't keep it. >> >> >> Oh but yes you can >> >> Existing database contents over 5000 records order by ID DESC >> > >Are you really so dense? This is NOT something inherent in the database. >It's only the OUTPUT that's ordered. Hell. It's just a shame you guys can't read between the lines of course it's the output. I assumed you guys were clever enough to work that out but apparently NOT. >> Therefore the order the data is written affect results of previously >> written scripts > >Nonsense. |
|
02-28-2008, 07:06 AM
| ||||
| ||||
| Re: php/mysql query insert values into enters the records in reverse order On Wed, 02 Nov 2005 10:32:00 +0000, Techie Guy <out@thepub.com> wrote: >On Wed, 02 Nov 2005 00:13:17 +0100, Christian Kirsch <ck@bru6.de> >wrote: > >>Techie Guy wrote: >>> On Tue, 01 Nov 2005 18:09:27 +0100, Christian Kirsch <ck@bru6.de> >>> wrote: >>> >>> >>>>Techie Guy wrote: >>>> >>>> >>>>>Yes I read the post and clearly understand that it doesn't matter >>>>>generally, what order data is entered into most databases. >>>>> >>>>>However in this case there are over 5000 records already in the >>>>>correct order in the database and it would be nice to keep them that >>>> >>>>May be you *read* the posting, but then you refuse to *understand*. >>>>THERE IS NO ORDER in a MySQL database. >>>> >>>> >>>>>way. >>>> >>>>Since there is no order, you can't keep it. >>> >>> >>> Oh but yes you can >>> >>> Existing database contents over 5000 records order by ID DESC >>> >> >>Are you really so dense? This is NOT something inherent in the database. >>It's only the OUTPUT that's ordered. Hell. > >It's just a shame you guys can't read between the lines of course it's >the output. So you ARE that dense. > >I assumed you guys were clever enough to work that out but apparently >NOT. Might I suggest that you claim you were just trolling? No, really. It'd be better than having everyone think you're an idiot. >>> Therefore the order the data is written affect results of previously >>> written scripts >> >>Nonsense. -- gburnore at DataBasix dot Com --------------------------------------------------------------------------- How you look depends on where you go. --------------------------------------------------------------------------- Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³ Black Helicopter Repair Services, Ltd.| Official Proof of Purchase ================================================== ========================= |
Linear Mode
