[ciapug] Mysql

[Tony Bibbs]

Yeah, I'm sure you guys thought it through...just hard as an outsider 
visualizing the circumstances that lead to the situation.

And for the record, I have no idea how you are having that particular 
problem.  Are you running those queries right inside the mysql client or 
via PHP?  I'm guessing you are using the mysql client but, if not, I'd 
do that to take out any chances PHP is part of the problem.

--Tony

Dave J. Hala Jr. wrote:
> On Fri, 2006-01-06 at 11:41, Tony Bibbs wrote:
> 
>>Well, not to open another can of worms but if the business requirements 
>>say you can't upgrade server software for another year-and-a-half I'd 
>>have assume there is one helluva good reason.
> 
> 
> There are a number of reasons. Many are too lengthly and some would not
> be appropriate to be discussed here. Working for the State I'm sure you
> understand.
> 
>>IMHO, 'running smoothly' isn't a good enough reason when you consider 
>>all the patches and upgrades that have been out (not to mention how many 
>>of them are security realted).  I would hope such an old codebase isn't 
>>accessible via the web.
> 
> 
> Actually, the code is running on php-4.3.2-23 on RHEL 3. It has also
> been well maintained. The system is fully updated, so security issues
> related to versioning and the platform are manageable.  As you know, RH
> back ports patches into the enterprise codebase. 
> 
> 
>>Also, here at the State I put together the migration plan to get our 
>>apps off PHP4/MySQL3.x to PHP5/MySQL4 and when the time comes, I'd 
>>strongly encourage you to do them seperately (i.e. upgrade PHP first 
>>then MySQL).
> 
> 
>>--Tony
>>
>>Dave J. Hala Jr. wrote:
>>
>>>I can't upgrade until Aug-Sept of 2007. Its a live well tested, mature
>>>working system. This server is also the replicating master for a number
>>>of other servers.
>>>
>>>Why this issue hasn't shown up in the last 3 years is beyond me. At this
>>>point, doing that upgrade would be like buying a new car because I've
>>>got a flat tire.
>>>
>>>However, in 07' I'll probably move to mysql 5.0 and php 5, so the plan
>>>is in the works.
>>>
>>>With regard to your question regarding the select returning 1281, the
>>>answer is yes. I just don't undertand  why the query doesn't move all
>>>the records when using the wildcard.
>>>
>>>
>>>
>>>:) Dave
>>>
>>>
>>>
>>>On Fri, 2006-01-06 at 11:11, David Champion wrote:
>>>
>>>
>>>>Dave J. Hala Jr. wrote:
>>>>
>>>>
>>>>>I'm running  mysql 3.23.58.  I've run into an issue inserting records
>>>>>into a table. The query criterion tells me there are 1281 records. When
>>>>>I do the insert mysql only only inserts 591 records.
>>>>>
>>>>>Here's the insert query:
>>>>>
>>>>>INSERT INTO notify_temp SELECT * FROM lhpl_side WHERE SNP='0';
>>>>>
>>>>>Anyone got any ideas as to why it skips/throws out 690 records?
>>>>>
>>>>>
>>>>>
>>>>>:) Dave
>>>>
>>>>So you mean if you say "SELECT count(*) FROM lhpl_side WHERE SNP='0'" it 
>>>>returns 1281?
>>>>
>>>>You might want to look into upgrading your mysql version. 3.23.58 was 
>>>>released on 9/11/2003. That's ancient.
>>>>
>>>>Going up to 4.1.x, or even 5.x would get you some nice performance 
>>>>improvments, as well as several nice features, like sub selects...
>>>>
>>>>-dc
>>>>
>>>>_______________________________________________
>>>>ciapug mailing list
>>>>ciapug at cialug.org
>>>>http://cialug.org/mailman/listinfo/ciapug
>>
>>_______________________________________________
>>ciapug mailing list
>>ciapug at cialug.org
>>http://cialug.org/mailman/listinfo/ciapug