Thread: [Phplib-trackers] [ phplib-Bugs-542811 ] nextid() uses mysql_query
Brought to you by:
nhruby,
richardarcher
Menu
▾
▴
phplib-trackers
|
From: <no...@so...> - 2002-04-12 03:18:28
|
Bugs item #542811, was opened at 2002-04-11 22:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS Status: Open Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
|
From: <no...@so...> - 2002-04-12 05:23:47
|
Bugs item #542811, was opened at 2002-04-12 13:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS Status: Open Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- >Comment By: Richard Archer (richardarcher) Date: 2002-04-12 15:23 Message: Logged In: YES user_id=279311 It does this so as to not trash the $this->Record array. The script could conceivably be looping through this array and using next_id() for each element! ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
|
From: <no...@so...> - 2002-04-12 15:40:05
|
Bugs item #542811, was opened at 2002-04-11 22:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS Status: Open Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- >Comment By: Layne Weathers (layne_weathers) Date: 2002-04-12 10:40 Message: Logged In: YES user_id=278685 I guess this is in the case of duplicating or moving data from one table to another. In that case, I would need to have two database objects - one to query the old table and the second to insert into the new table (if I tried to use only one object I would lose my select results) so I might as well nextid() with the second object. I guess I could save all the data in an array, but then I don't see any reason not to get the id later when I'm looping through the array. ---------------------------------------------------------------------- Comment By: Richard Archer (richardarcher) Date: 2002-04-12 00:23 Message: Logged In: YES user_id=279311 It does this so as to not trash the $this->Record array. The script could conceivably be looping through this array and using next_id() for each element! ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
|
From: <no...@so...> - 2002-07-02 19:52:06
|
Bugs item #542811, was opened at 2002-04-11 23:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS Status: Open Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- >Comment By: nathan hruby (nhruby) Date: 2002-07-02 15:52 Message: Logged In: YES user_id=19736 So is this a bug? It seems like it isn't. ---------------------------------------------------------------------- Comment By: Layne Weathers (layne_weathers) Date: 2002-04-12 11:40 Message: Logged In: YES user_id=278685 I guess this is in the case of duplicating or moving data from one table to another. In that case, I would need to have two database objects - one to query the old table and the second to insert into the new table (if I tried to use only one object I would lose my select results) so I might as well nextid() with the second object. I guess I could save all the data in an array, but then I don't see any reason not to get the id later when I'm looping through the array. ---------------------------------------------------------------------- Comment By: Richard Archer (richardarcher) Date: 2002-04-12 01:23 Message: Logged In: YES user_id=279311 It does this so as to not trash the $this->Record array. The script could conceivably be looping through this array and using next_id() for each element! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
|
From: <no...@so...> - 2002-08-07 19:32:06
|
Bugs item #542811, was opened at 2002-04-11 22:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS >Status: Closed Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- Comment By: nathan hruby (nhruby) Date: 2002-07-02 14:52 Message: Logged In: YES user_id=19736 So is this a bug? It seems like it isn't. ---------------------------------------------------------------------- Comment By: Layne Weathers (layne_weathers) Date: 2002-04-12 10:40 Message: Logged In: YES user_id=278685 I guess this is in the case of duplicating or moving data from one table to another. In that case, I would need to have two database objects - one to query the old table and the second to insert into the new table (if I tried to use only one object I would lose my select results) so I might as well nextid() with the second object. I guess I could save all the data in an array, but then I don't see any reason not to get the id later when I'm looping through the array. ---------------------------------------------------------------------- Comment By: Richard Archer (richardarcher) Date: 2002-04-12 00:23 Message: Logged In: YES user_id=279311 It does this so as to not trash the $this->Record array. The script could conceivably be looping through this array and using next_id() for each element! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
|
From: <no...@so...> - 2002-08-07 21:29:35
|
Bugs item #542811, was opened at 2002-04-12 13:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 Category: DB_SQL Group: current CVS Status: Closed Resolution: None Priority: 2 Submitted By: Layne Weathers (layne_weathers) Assigned to: Layne Weathers (layne_weathers) Summary: nextid() uses mysql_query Initial Comment: nextid() uses mysql_query() and mysql_fetch_array() instead of using DB_Sql's own error-checking functions. ---------------------------------------------------------------------- >Comment By: Richard Archer (richardarcher) Date: 2002-08-08 07:29 Message: Logged In: YES user_id=279311 I reckon the class is designed that way to allow greater flexibility. I can see where Layne is coming from though... perhaps you should be using a separate instantiation of the class to perform different operations. Perhaps there should be some *gasp* comments added to the code to clarify this. ---------------------------------------------------------------------- Comment By: nathan hruby (nhruby) Date: 2002-07-03 05:52 Message: Logged In: YES user_id=19736 So is this a bug? It seems like it isn't. ---------------------------------------------------------------------- Comment By: Layne Weathers (layne_weathers) Date: 2002-04-13 01:40 Message: Logged In: YES user_id=278685 I guess this is in the case of duplicating or moving data from one table to another. In that case, I would need to have two database objects - one to query the old table and the second to insert into the new table (if I tried to use only one object I would lose my select results) so I might as well nextid() with the second object. I guess I could save all the data in an array, but then I don't see any reason not to get the id later when I'm looping through the array. ---------------------------------------------------------------------- Comment By: Richard Archer (richardarcher) Date: 2002-04-12 15:23 Message: Logged In: YES user_id=279311 It does this so as to not trash the $this->Record array. The script could conceivably be looping through this array and using next_id() for each element! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=403611&aid=542811&group_id=31885 |
Thanks for helping keep SourceForge clean.
X