473,396 Members | 1,774 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,396 software developers and data experts.

looping through MySQL to change the id (using PHP) to equal the number of rows

PG
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?
Jul 19 '05 #1
6 4018
BDR
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?


Jul 19 '05 #2
BDR
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?


Jul 19 '05 #3
BDR
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:

(Of course, this is done with Perl here, not PHP like you're using - but
you should be able to grasp the concept anyway)...
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?


Jul 19 '05 #4
BDR
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:

(Of course, this is done with Perl here, not PHP like you're using - but
you should be able to grasp the concept anyway)...
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?


Jul 19 '05 #5
PG
Yes thankyou. Here is the code in PHPL:.

$x=0;
$query1 = mysql_query ("SELECT * FROM counter", $db);
while( $therow = mysql_fetch_array($query1) )
{
$x++;
$therow_id = $therow[id];
$query2 = "UPDATE counter SET id='$x' WHERE id='$therow_id' limit 1";
$aResult = mysql_query($query2);
}
BDR <jo*@noemail.com> wrote in message news:<3F**************@noemail.com>...
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:

(Of course, this is done with Perl here, not PHP like you're using - but
you should be able to grasp the concept anyway)...
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?

Jul 19 '05 #6
PG
Yes thankyou. Here is the code in PHPL:.

$x=0;
$query1 = mysql_query ("SELECT * FROM counter", $db);
while( $therow = mysql_fetch_array($query1) )
{
$x++;
$therow_id = $therow[id];
$query2 = "UPDATE counter SET id='$x' WHERE id='$therow_id' limit 1";
$aResult = mysql_query($query2);
}
BDR <jo*@noemail.com> wrote in message news:<3F**************@noemail.com>...
You have no "WHERE" clause on your $Query.

So it iterated through the loop, and updated ALL records in the database
with the $counting.... each time. In essence, each time the query
executed, it updated 22 records with the same id number. You're simply
seeing the last query result.

Update counter set id='$id'

Updates ALL rows with that id number.

update counter set id='$id' where id='$currentnumber' will isolate it
row by row. But you've got to get the $currentnumber first.

You can do this using a fetchall array ref in one query, and an active
update with where:

(Of course, this is done with Perl here, not PHP like you're using - but
you should be able to grasp the concept anyway)...
#------------------------------------------------------------
$x=0;
$query=qq~select `id` from counter~;
$sth=$dbh->prepare($query);
$sth->execute || print "Error: $DBI::errstr\n";
$id_num = $sth->fetchall_arrayref() or die "$DBI::errstr\n";
$last_row = $#{$id_num};
$last_col = $#{$id_num->[$row_index]};
$sth->finish;
foreach $row_index(0..$last_row){
$x++;
$currentnumber=$id_num->[$row_index][0];
$query=qq~update counter set `id`='$x' where `id`='$currentnumber'
limit 1~;
$dbh->do($query);
}
#-------------------------------------------------------------
- or by using two statement handles (2 dbd connections) simultaneously:

$x=0;
$query1=qq~select `id` from counter~;
$sth1=$dbh1->prepare($query1);
$sth1->execute;
while(@row=$sth1->fetchrow){
$x++;
$query2=qq~update counter set `id`='$x' where `id`='$row[0]' limit 1~;
$dbh2->do($query2);
}
$sth->finish;
#--------------------------------------------------------------
A little simplistic, but I think it will fix the 22 rows with the same
number due to the limit 1 part of the query. If not, then you'll have
to manually change all of the row id numbers to fix it. (Good thing this
was done on a table with only 22 rows... always have a backup).

Actually, this manipulation of reference numbers is a bad idea, unless
it's just for your own single personal use.

Here's why:
If your database is to be edited/addedto/deleted by multiple users
(simultaneous web users?), you can get into trouble by changing key id's
this way. For instance, if you've got a user entering info into the
database on a specific record referenced by the $id, and the entry
hasn't been submitted yet... and you... update your database using this
method and changing all of the reference id's, once the user submits the
record update, guess what-> the original reference id will have been
renumbered/renamed by the routine, and the table update is done on the
wrong record.

Just some food for thought.

Good luck.
PG wrote:
When deleting a row from the database, that id is now missing.
So what I'm trying to do is update in a loop (maybe an sql loop if
there is one) of all of the id numbers - sort of like renaming them.
It did partly work because all the id's were set to 22. Thats because
there was 22 rows.

Here's the code I used:

$result = mysql_query ("SELECT * FROM counter");
for($counting = 1; $row = mysql_fetch_row ($result); ++$counting)
{
$id = $counting;
print("-- -#1-IDcounting=$id ");
$Query = "UPDATE counter SET id='$id' ";
$aResult = mysql_query($Query);
$id = 0;
print("-- -#2-IDcounting=$id ");
print("<BR>");
}
//$aResult = mysql_query($Query); //not sure if I need it again

The result was:

-- -#1-IDcounting=1 -- -#2-IDcounting=0
-- -#1-IDcounting=2 -- -#2-IDcounting=0
-- -#1-IDcounting=3 -- -#2-IDcounting=0 ... etc

It looks like its working, however when accessing the database all the
id's were set to 22.

Did I do something wrong in the loop or is there some other way?

Jul 19 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Reply via newsgroup | last post by:
Folks, When performing an update in mysql (using PHP), can I find out how many records were matched? mysql_affected_rows() won't work... and I have the following problem that I thought I...
2
by: Phil Powell | last post by:
Relevancy scores are normally defined by a MySQL query on a table that has a fulltext index. The rules for relevancy scoring will exclude certain words due to their being too short (minimum...
0
by: Phil Powell | last post by:
The table already has a fulltext index and from there I can use the MySQL fulltext search query to get results as well as the relevancy score. The problem I have is that MySQL has a default...
0
by: Philip Stoev | last post by:
Hi all, Please tell me if any of this makes sense. Any pointers to relevant projects/articles will be much appreciated. Philip Stoev http://www.stoev.org/pivot/manifest.htm ...
0
by: Mike Chirico | last post by:
Interesting Things to Know about MySQL Mike Chirico (mchirico@users.sourceforge.net) Copyright (GPU Free Documentation License) 2004 Last Updated: Mon Jun 7 10:37:28 EDT 2004 The latest...
57
by: Bing Wu | last post by:
Hi all, I am running a database containing large datasets: frames: 20 thousand rows, coordinates: 170 million row. The database has been implemented with: IBM DB2 v8.1
6
by: Ridge Burner | last post by:
Can someone tell me which of these 2 SQL queries will be more efficient? I'm having a debate with another guy about which would be less resource intensive for MySQL. The first uses MySQL to pick...
6
Atli
by: Atli | last post by:
This is an easy to digest 12 step guide on basics of using MySQL. It's a great refresher for those who need it and it work's great for first time MySQL users. Anyone should be able to get...
2
nine72
by: nine72 | last post by:
Hi, first I want to say thanks for the help I received here over a year ago with a perplexing issue that I had. The advise was fantastic and helped a lot. Today I have another issues that I can...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.