Welcome, Guest. Please Login or Register.
August 28, 2025, 11:54:31 AM
Home Help Search Log in Register
News: SMF is the next generation in forum software, almost completely re-written from the ground up, make sure you don't fall for cheap imitations that suffer from feature bloat!

YaBB SE Community  |  English User Help  |  English Help  |  No MySQL vs. MySQL... « previous next »
Pages: [1] Reply Ignore Print
Author Topic: No MySQL vs. MySQL...  (Read 908 times)
Bradley
Noobie
*
Posts: 17


A Self Portrait!

ICQ - 134536518bradley@leafsforever.ca WWW
No MySQL vs. MySQL...
« on: April 06, 2002, 08:10:55 PM »
Reply with quote

Here is my options:
- 10 megs with MySQL
- 40 megs without MySQL

In other words, which board would be more efficient for me. I could use 40 megs with a perl board, but only 10 megs with a YaBB Se. Apparently, the database is counted in the 10 megs. Is that true? I thought the database could be any size.

So, what should be best for me?

Also, my site uses about 4 megs before with no messages due to a lot of content. So, would the MySQL be more compact to fit in 6 megs, compared to 36 megs of text files?
Logged

Shoeb Omar
Disciple of Joe
YaBB God
*****
Posts: 1420


The shrub demands war. I don't. The world doesn't.

ICQ - 69234983clickopedia@hotmail.com WWW
Re:No MySQL vs. MySQL...
« Reply #1 on: April 06, 2002, 09:16:45 PM »
Reply with quote

id have to say 36 mb of text files..
Logged

"If we all practice an eye for an eye, pretty soon the whole world will be blind" - Gandhi

We need to start listening to advocates of peace in oder to advance society. We have not grown from the prehistoric barbarians we once were.  Will society ever mature?
Pages: [1] Reply Ignore Print 
YaBB SE Community  |  English User Help  |  English Help  |  No MySQL vs. MySQL... « previous - next »
 


Powered by MySQL Powered by PHP YaBB SE Community | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
SMF 2.1.4 © 2023, Simple Machines
Valid XHTML 1.0! Valid CSS

Page created in 0.010 seconds with 16 queries.