dbTalk Databases Forums  

too many columns/rows?

comp.databases.mysql comp.databases.mysql


Discuss too many columns/rows? in the comp.databases.mysql forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
geoff@invalid.invalid
 
Posts: n/a

Default too many columns/rows? - 05-21-2011 , 03:43 PM






Hello

I know that I could organise the data better but does phpmyadmin or
mysql have a problem with a table which has 600 columns and 100 rows?

Each column holds approx. 10 chrs.

Cheers

Geoff

Reply With Quote
  #2  
Old   
geoff@invalid.invalid
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 03:46 PM






On Sat, 21 May 2011 21:43:46 +0100, geoff (AT) invalid (DOT) invalid wrote:

Quote:
Hello

I know that I could organise the data better but does phpmyadmin or
mysql have a problem with a table which has 600 columns and 100 rows?

Each column holds approx. 10 chrs.
Good grief! I should have written that each of the 600 fields holds
approx. 10 chrs.

Geoff

Quote:
Cheers

Geoff

Reply With Quote
  #3  
Old   
onedbguru
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 04:37 PM



On May 21, 4:46*pm, ge... (AT) invalid (DOT) invalid wrote:
Quote:
On Sat, 21 May 2011 21:43:46 +0100, ge... (AT) invalid (DOT) invalid wrote:
Hello

I know that I could organise the data better but does phpmyadmin or
mysql have a problem with a table which has 600 columns and 100 rows?

Each column holds approx. 10 chrs.

Good grief! I should have written that each of the 600 fields holds
approx. 10 chrs.

Geoff







Cheers

Geoff

Have your RTFineM?
http://dev.mysql.com/doc/refman/5.6/...unt-limit.html

Do yourself a favor and figure out how to do data normalization and
change it now before you get to the breaking point.

IIRC phpadmin should be able to handle what ever the maximums are for
mysql.

Reply With Quote
  #4  
Old   
richard
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 09:33 PM



On Sat, 21 May 2011 14:37:32 -0700 (PDT), onedbguru wrote:

Quote:
On May 21, 4:46*pm, ge... (AT) invalid (DOT) invalid wrote:
On Sat, 21 May 2011 21:43:46 +0100, ge... (AT) invalid (DOT) invalid wrote:
Hello

I know that I could organise the data better but does phpmyadmin or
mysql have a problem with a table which has 600 columns and 100 rows?

Each column holds approx. 10 chrs.

Good grief! I should have written that each of the 600 fields holds
approx. 10 chrs.

Geoff







Cheers

Geoff


Have your RTFineM?
http://dev.mysql.com/doc/refman/5.6/...unt-limit.html

Do yourself a favor and figure out how to do data normalization and
change it now before you get to the breaking point.

IIRC phpadmin should be able to handle what ever the maximums are for
mysql.
Max columns is 1,000.
don't recall off hand what it is for rows. Maybe 1,000 as well.

Reply With Quote
  #5  
Old   
Doug Miller
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 09:59 PM



In article <4fvq048sawyg.dlg (AT) evanplatt (DOT) sux>, richard <member (AT) newsguy (DOT) com> wrote:
Quote:
On Sat, 21 May 2011 14:37:32 -0700 (PDT), onedbguru wrote:

On May 21, 4:46*pm, ge... (AT) invalid (DOT) invalid wrote:
On Sat, 21 May 2011 21:43:46 +0100, ge... (AT) invalid (DOT) invalid wrote:
Hello

I know that I could organise the data better but does phpmyadmin or
mysql have a problem with a table which has 600 columns and 100 rows?

Each column holds approx. 10 chrs.

Good grief! I should have written that each of the 600 fields holds
approx. 10 chrs.

Geoff







Cheers

Geoff


Have your RTFineM?
http://dev.mysql.com/doc/refman/5.6/...unt-limit.html

Do yourself a favor and figure out how to do data normalization and
change it now before you get to the breaking point.

IIRC phpadmin should be able to handle what ever the maximums are for
mysql.

Max columns is 1,000.
don't recall off hand what it is for rows. Maybe 1,000 as well.
Ummm.... no. It's a little bit higher than that.

To the OP: 600 columns is *strongly* suggestive of a very poor database
design. What are these 600 columns, anyway?

Reply With Quote
  #6  
Old   
Beauregard T. Shagnasty
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 10:56 PM



richard the sto0pid wrote:

Quote:
Max columns is 1,000.
Wrong again, Robin.
http://dev.mysql.com/doc/refman/5.0/...unt-limit.html

Quote:
don't recall off hand what it is for rows. Maybe 1,000 as well.
Wrong again, Robin.
There is no Maximum Number of Records in a table.
There can be a limitation about hardware.

--
-bts
-In a broadband world, you are just a dialup

Reply With Quote
  #7  
Old   
richard
 
Posts: n/a

Default Re: too many columns/rows? - 05-21-2011 , 11:30 PM



On Sat, 21 May 2011 23:56:01 -0400, Beauregard T. Shagnasty wrote:

Quote:
richard the sto0pid wrote:

Max columns is 1,000.

Wrong again, Robin.
http://dev.mysql.com/doc/refman/5.0/...unt-limit.html

don't recall off hand what it is for rows. Maybe 1,000 as well.

Wrong again, Robin.
There is no Maximum Number of Records in a table.
There can be a limitation about hardware.
<quote from your source>
There is a hard limit of 4096 columns per table, but the effective maximum
may be less for a given table. The exact limit depends on several
interacting factors, listed in the following discussion.
</quote>

So yes there are even row limits.
You just have to figure it out.

Reply With Quote
  #8  
Old   
geoff@invalid.invalid
 
Posts: n/a

Default Re: too many columns/rows? - 05-22-2011 , 01:31 AM



On Sun, 22 May 2011 02:59:28 GMT, dougatmilmacdotcom (AT) example (DOT) com (Doug
Miller) wrote:

Quote:
To the OP: 600 columns is *strongly* suggestive of a very poor database
design. What are these 600 columns, anyway?
Doug,

You are right no doubt but I have tried once and gave up. I will look
again.

What happens is that the user may respond to all of 120
sections/tests, each with 5 fields for data input into the table.

It is important that I can know that all these were done in the same
session. At the moment I do this by using 1 table and having the
user's username, password and the date/time.

How would I know that all sections were attempted in the same session
if I had separate tables for each section?

Cheers

Geoff

Reply With Quote
  #9  
Old   
Tony Mountifield
 
Posts: n/a

Default Re: too many columns/rows? - 05-22-2011 , 02:11 AM



In article <c3bht6d1u0jjit1itj6t45rktohhuiojum (AT) 4ax (DOT) com>,
<geoff (AT) invalid (DOT) invalid> wrote:
Quote:
On Sun, 22 May 2011 02:59:28 GMT, dougatmilmacdotcom (AT) example (DOT) com (Doug
Miller) wrote:

To the OP: 600 columns is *strongly* suggestive of a very poor database
design. What are these 600 columns, anyway?

Doug,

You are right no doubt but I have tried once and gave up. I will look
again.

What happens is that the user may respond to all of 120
sections/tests, each with 5 fields for data input into the table.

It is important that I can know that all these were done in the same
session. At the moment I do this by using 1 table and having the
user's username, password and the date/time.

How would I know that all sections were attempted in the same session
if I had separate tables for each section?

Cheers

Geoff
Think of a separate table per entity:

1. users table. This contains a userid field and all other information
about a user, such as name, email, password, etc.

2. sessions table. This contains information about a user's individual
session, and contains a sessionid, a userid (user whose session it is),
date/time, and any other session-specific items, such as IP address, etc.

3. sections table. This contains the information about the user's responses
to a specific section in a given session. It contains sectionid, a sessionid
(session this section belongs to), and the five answers to that section.
It will also want either a section number 1-120, or else the id of a record
in a fourth table that contains the details of the original section.

Hope this helps.

Cheers
Tony

--
Tony Mountifield
Work: tony (AT) softins (DOT) co.uk - http://www.softins.co.uk
Play: tony (AT) mountifield (DOT) org - http://tony.mountifield.org

Reply With Quote
  #10  
Old   
geoff@invalid.invalid
 
Posts: n/a

Default Re: too many columns/rows? - 05-22-2011 , 02:33 AM



On Sun, 22 May 2011 07:11:03 +0000 (UTC), tony (AT) mountifield (DOT) org (Tony
Mountifield) wrote:

Quote:
In article <c3bht6d1u0jjit1itj6t45rktohhuiojum (AT) 4ax (DOT) com>,
geoff (AT) invalid (DOT) invalid> wrote:
On Sun, 22 May 2011 02:59:28 GMT, dougatmilmacdotcom (AT) example (DOT) com (Doug
Miller) wrote:

To the OP: 600 columns is *strongly* suggestive of a very poor database
design. What are these 600 columns, anyway?

Doug,

You are right no doubt but I have tried once and gave up. I will look
again.

What happens is that the user may respond to all of 120
sections/tests, each with 5 fields for data input into the table.

It is important that I can know that all these were done in the same
session. At the moment I do this by using 1 table and having the
user's username, password and the date/time.

How would I know that all sections were attempted in the same session
if I had separate tables for each section?

Cheers

Geoff

Think of a separate table per entity:

1. users table. This contains a userid field and all other information
about a user, such as name, email, password, etc.

2. sessions table. This contains information about a user's individual
session, and contains a sessionid, a userid (user whose session it is),
date/time, and any other session-specific items, such as IP address, etc.

3. sections table. This contains the information about the user's responses
to a specific section in a given session. It contains sectionid, a sessionid
(session this section belongs to), and the five answers to that section.
It will also want either a section number 1-120, or else the id of a record
in a fourth table that contains the details of the original section.

Hope this helps.

Cheers
Tony
Tont

Very helpful - thanks! Will give it a try.

Cheers

Geoff

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.