|
|
Posted by Tom on 05/10/07 16:49
"cluthz" <WHATEEVVEERR@by.co.uk> wrote in message
news:BuR%h.14704$Ro3.500@text.news.blueyonder.co.uk...
>
> Further details of the query was as follows.
> It was PHP4/ MYsql 3 (unfortunlety).
>
> I did not actually request all 35 fields, only about 4 of them. I needed
to
> do all rows as this is a one off change. Basically on a customer details
we
> were moving from storing the email address into the main customer details
> into a separate table so that the customer can have more then one email
> address stored.
>
> In fact it has caused all sorts of other challenges which not doubt you
guys
> will hear about, but I fixed this problem by just rather then making it
> update the new table in a sub routine which called again to a connection
to
> a database, I just done it within the main routine itself. Made it bigger
> but as one off seems to work fine when I do this.
>
> Really I would still expect it to work with the sub routine, and would
like
> to fully understand why it didn't. but I guess I'm just working with alot
of
> data.
>
> Thanks
>
>
There is a "mysql_free_result()" function that may help you out if the size
of your results is affecting you. I don't think you could use it on your
initial query with your primary connection, since you need to work from that
list, but may be able to use the on you secondary connection to clear the
results after each mysql_query().
Tom
--
Newsguy.com
90+ Days Retention
Higher levels of article completion
Broader newsgroups coverage
Navigation:
[Reply to this message]
|