b3ta.com board
You are not logged in. Login or Signup
Home » Messageboard » Message 4219599 (Thread)

# that all depends
on all sorts of things like row lengths, the query you are running and the way the wind is blowing.

But you should be able to create indexes on the heavier tables to reduce the impact

*Removes DBA hat*
(I helped save b3ta! dazzla - Just blew up his shuttle and potentially lost all pr0n, Wed 2 Feb 2005, 11:31, archived)
# oh well... i'll give it a go, most of the columns will be storing boolean values
and there will only be a couple with any sizable amount of data in...
(I helped save b3ta! lemony, Wed 2 Feb 2005, 11:36, archived)
# the storage for a boolean in mysql is actually 2048K

*lies through teeth*
(I helped save b3ta! Reckless_Rik, Wed 2 Feb 2005, 11:43, archived)
# hahahahaha
you <sub>ed that enough that i nearly didn't notice it
(I helped save b3ta! lemony, Wed 2 Feb 2005, 11:46, archived)
# well if it's mostly boolean
then you should be fine for hundreds probably even thousands of rows.
(I helped save b3ta! dazzla - Just blew up his shuttle and potentially lost all pr0n, Wed 2 Feb 2005, 11:46, archived)
# grand stuff...
*prepares unnesecarily long select statements*
(I helped save b3ta! lemony, Wed 2 Feb 2005, 11:49, archived)
# rows or columns...?!
don`t do thousands of columns (fields man... use the correct term!), whether or not the database supports it
(I helped save b3ta! Reckless_Rik, Wed 2 Feb 2005, 11:55, archived)
# arse
i did actually mean rows, thousands of fields (thanks for the correction) would be hideous to use.
(I helped save b3ta! dazzla - Just blew up his shuttle and potentially lost all pr0n, Wed 2 Feb 2005, 12:04, archived)
# Technically attributes
and tuples instead of rows

/splitting hairs
(I helped save b3ta! dingochutney *parp*, Wed 2 Feb 2005, 12:07, archived)