Message
From: Richard Reina gatorre...@gmail.com
Reply-To: Richard Reina gatorre...@gmail.com
Date: 07/29/15 10:19 AM
To: mysql@lists.mysql.com mysql@lists.mysql.com
Cc:
Sub: table design question
If I were to create a database table(s) to tract most common repairs to
different appliances I
Hi Richard,
On 7/29/2015 10:19 AM, Richard Reina wrote:
If I were to create a database table(s) to tract most common repairs to
different appliances I can't decide if it would be better to create one
table with a long ENUM column that contains repairs that could be
attributed to any appliance
If I were to create a database table(s) to tract most common repairs to
different appliances I can't decide if it would be better to create one
table with a long ENUM column that contains repairs that could be
attributed to any appliance or different repair tables for each appliance.
All the
From: Richard Reina gatorre...@gmail.com
I want to create a US geography database. So far I have categories such as
state nick names (some states have more than one), state mottos (text 25 to
150 characters), state name origins (100-300 characters), state trivial
facts, entry into union.
I want to create a US geography database. So far I have categories such as
state nick names (some states have more than one), state mottos (text 25 to
150 characters), state name origins (100-300 characters), state trivial
facts, entry into union. My question is; would it be better to keep at
-Original Message-
From: Richard Reina [mailto:gatorre...@gmail.com]
Sent: Monday, September 19, 2011 9:55 AM
To: mysql@lists.mysql.com
Subject: table design question
I want to create a US geography database. So far I have categories such as
state nick names (some states have more than
I would design three tables:
Table1 (states):
ID, name, abbreviation
Table2 (state_item):
ID, state_id (from states), item_id (from item_type), item_value (varchar)
Table3 (item_type):
ID, item_name
Into the item_type table you can insert:
Nick Name
Motto
Name origin
Facts
SomeOtherDataPoint
Thank you very much for all the insightful advice. I will keep the
separated.
2011/9/19 Jerry Schwartz je...@gii.co.jp
-Original Message-
From: Richard Reina [mailto:gatorre...@gmail.com]
Sent: Monday, September 19, 2011 9:55 AM
To: mysql@lists.mysql.com
Subject: table design
Hi,
I'm creating a application which hosts football matches and I want to record
the player appearances, goals etc. I was thinking of having a record for
each player as follows :
appearance_id
season_id
player_id
team_id
competition_id
appearance
goals
yellow_card
red_card
date_played
Is this
I have been looking at stock photo sites lately, started wondering how they
are doing their keyword searched. Given a potential for millions of images,
each with x keywords, I have come up with two approaches...
Approach one
Images table, with a parent id
Keywords table, each keyword would be
Ysgrifennodd Scott Haneda:
I have been looking at stock photo sites lately, started wondering how they
are doing their keyword searched. Given a potential for millions of images,
each with x keywords, I have come up with two approaches...
snip /
Is this the sort of thing you're looking
Greetings,
Buy 'Building Scalable Web Sites'
[http://www.oreillynet.com/pub/pr/1582], authored by the chief
architect of Flickr. Among other interesting topics, he describes the
system they use for full-text search. Its pretty simple, though this
is just one of the ways you can solve this
This isn't exactly what I was looking for, but it works like a charm for
both my needs and the sys admins.
Go figure everyone is happy now!
Many Thanks!
-Tyler
Kishore Jalleda wrote:
The delete would definitely depend upon the size of the record set being
deleted, anyway assuming I
I'm trying to wrap my head around a performance problem our institution is
having on our Mysql Server which hosts all of our logs from around campus.
Specifically our MailLogs tables.
What I'm having a hard time with is we have metadata such as:
CREATE TABLE mail00 (
host varchar(32)
The delete would definitely depend upon the size of the record set being
deleted, anyway assuming I comprehended your situation correctly ,I would
suggest using the Merge storage engine for your needs , and keep every
single day of data in a seperate MyISAM table, and merge all those tables
into the table.
-Original Message-
From: Kishore Jalleda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 31, 2007 8:51 AM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: Database Layout (Design) Question
The delete would definitely depend upon the size of the record set
In the last episode (Jan 31), [EMAIL PROTECTED] said:
I'm trying to wrap my head around a performance problem our
institution is having on our Mysql Server which hosts all of our logs
from around campus.
Specifically our MailLogs tables.
What I'm having a hard time with is we have
I want to design a database for lots of users. Each user will be
managing their own messages. Does it make sense to create a table
for each user after they've registered?
Or should I just create one MESSAGES table and store messages there
keyed off of their user_id?
If I create a table
I want to design a database for lots of users. Each user will be managing
their own messages. Does it make sense to create a table for each user after
they've registered?
Or should I just create one MESSAGES table and store messages there keyed off
of their user_id?
If I create a table for
: Database design question
I want to design a database for lots of users. Each user will be managing
their own messages. Does it make sense to create a table for each user
after they've registered?
Or should I just create one MESSAGES table and store messages there keyed
off of their user_id?
If I
referencing the destinating user as well.
-Original Message-
From: James Tu [mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 1:56 PM
To: mysql@lists.mysql.com
Subject: Database design question
I want to design a database for lots of users. Each user will be
managing
their own
@lists.mysql.com
Sent: Monday, August 07, 2006 4:11 PM
Subject: Re: Database design question
Thanks everyone.
Now I feel confident that one table will be fine (Tripp's stat of
30 million records put me at ease :) ).
Cheers,
-James
On Aug 7, 2006, at 4:08 PM, John Meyer wrote:
One table,
USERS
On 8/7/06, James Tu [EMAIL PROTECTED] wrote:
If I create a table for each user (I can potentially have hundreds of
thousands of users), will MySQL be able to handle this?
If I just have one table, I could potentially have millions of
records in one table. Will MySQL be able to handle this?
Scott Klarenbach wrote:
These are the tables in question:
RFQ (Request for Quote)
Part
Inventory
Inventory items ALWAYS have a partID.
RFQ items ALWAYS have a partID.
However, sometimes, RFQ items have an inventoryID as well. Now, we have a
redundancy problem. Because, in those instances
These are the tables in question:
RFQ (Request for Quote)
Part
Inventory
Inventory items ALWAYS have a partID.
RFQ items ALWAYS have a partID.
However, sometimes, RFQ items have an inventoryID as well. Now, we have a
redundancy problem. Because, in those instances when the RFQ has an
Scott,
I'm sure this type of problem is run up against all the time, and I'm
wondering what the best practice methodology is from experienced DBA's.
It looks like the kind of problem database schemas are meant to
_avoid_.
>From your description it seems you have ...
part (
partID PRIMARY
Hi,
A very simple question. I have two products at our
website and i would like to keep track of how many of
each softwares were downloaded daily.
I am planning to create the following table:
id - auto_incr
date_of_download - data
product_name - enum value containing the two products
Then I
Greetings list,
In an analysis I was sent, there is 1 table with a simple set of rules, e.g.
a_table (id, day, max_hours, min_hours, min_days, start_time, stop_time,
max_attendants, ...)
No biggie there.
The problem is the user has to be able to define exceptions to those rules.
These
Hi All,
I'm not sure the best design approach for a product table for a number
of different hardware devices. Some devices have IP, Port, CPU, Memory
specs, whilst some don't. Current desing is below.
Products:
product_id
product_name
maker_id
controller_id
product_type_id
Mark Sargent [EMAIL PROTECTED] wrote on 06/03/2005 03:04:23 AM:
Hi All,
I'm not sure the best design approach for a product table for a number
of different hardware devices. Some devices have IP, Port, CPU, Memory
specs, whilst some don't. Current desing is below.
Products:
product_id
Hi, here is the case:
one student may have more than one address, and one student may have more
than one phone number
so the db would be:
student
student_id
name
age
address
---
address_id
student_id
street_name
phone_num
--
student_id
num
, May 24, 2005 1:34 PM
To: mysql@lists.mysql.com
Subject: DB design question
Hi, here is the case:
one student may have more than one address, and one student may have more
than one phone number
so the db would be:
student
student_id
name
age
address
---
address_id
PROTECTED]
Sent: Tuesday, May 24, 2005 1:34 PM
To: mysql@lists.mysql.com
Subject: DB design question
Hi, here is the case:
one student may have more than one address, and one student may have
more than one phone number
so the db would be:
student
student_id
name
age
address
From: Koon Yue Lam [mailto:[EMAIL PROTECTED]
Hi, here is the case:
one student may have more than one address, and one student
may have more than one phone number
so the db would be:
student
student_id
name
age
address
---
address_id
student_id
From: Mike Johnson [mailto:[EMAIL PROTECTED]
From: Koon Yue Lam [mailto:[EMAIL PROTECTED]
the problems is, when I want to query both student, address
and phone num, the sql will be
select * from student s, address a, phone_num n
where s.student_id = a.sudent_id
and s.student_id
Something like this would make more sense to me and provide greater
flexibility;
It doesn't to me...
student
student_id
name
age
address
---
address_id
street_name
city
state
zip
What addresses are these? Random addresses where a student _might_
PROTECTED]
Sent: Tuesday, May 24, 2005 12:34 PM
To: mysql@lists.mysql.com
Subject: DB design question
Hi, here is the case:
one student may have more than one address, and one student may have more
than one phone number
so the db would be:
student
student_id
name
age
address
Martijn Tonies [EMAIL PROTECTED] wrote on 05/24/2005 02:32:05 PM:
Something like this would make more sense to me and provide greater
flexibility;
It doesn't to me...
student
student_id
name
age
address
---
address_id
street_name
Shawn,
I agree with you that the tables can have different info with regard to
the requirements.
But for storing only addresses for specific students, this 4 table design
seems weirdish to me... I think it makes more sense to keep a
student_id in the Addresses table...
With regards,
Martijn
I have four different activities. Each has its own set of data that
I want to save. So, I made four different tables to hold the saved
data. Each record also has 'keywords' field (essentially this is the
only field that all tables have in common.)
Later on, I want to search all the keywords
james tu [EMAIL PROTECTED] wrote on 04/26/2005 12:06:34 PM:
I have four different activities. Each has its own set of data that
I want to save. So, I made four different tables to hold the saved
data. Each record also has 'keywords' field (essentially this is the
only field that all
I tried that and maybe I'm doing something wrong but...
-I have to select the same number of columns...for each UNION
-And each of the records from the union fall under the same column
headings as the first SELECT...
I even tried to define column aliases..
SELECT `running` as `running_blah`...
If you posted your actual table structures (SHOW CREATE TABLE xx\G) I
think I could be more helpful. Right now I am just shooting in the dark.
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
James [EMAIL PROTECTED] wrote on 04/26/2005 02:15:49 PM:
I tried that and
I haven't created real project tables yet.
But here are the test ones that I'm experimenting with.
CREATE TABLE east (
id int(11) NOT NULL auto_increment,
keywords varchar(255) default NULL,
east_1 varchar(255) default NULL,
PRIMARY KEY (id)
) ;
CREATE TABLE north (
north_id int(11) NOT
Hello,
I have two questions:
I would like to know whether I am violating the principle of atomicity in
doing the following:
I have a form which has a field with the following options: Choice1, choice2
and choice3.
Each of the above choices have two further subchoices : subChoice1,
subchoice2.
Mahmoud,
Are these values atomical?
My other question is what are the repercussions of
not putting a table in 2nd and 3rd Normal Form.
Your 'choice1-subchoice1' etc are combined values, so they aren't
atomic. From your three example dropdown values, it looks as if
'choice' and 'subchoice'
Hi all,
I have some doubts about how to implement this kind of scenario:
I have a table of elements in cronological order, let's call it table A:
for every A element, I have a number of elements ordered on a
progressive number.
This could be a simply one-to-many relation, where I can handle a
I think you need to explain what kind of SELECTs you want to do, and what
results you expect. How do you expect to get results from a SELECT which
returns hits in both the B and C tables? If you expect to do this, then
the D table is probably your correct answer. Do you really need a rec_type
Il giorno 11/ott/04, alle 11:53, [EMAIL PROTECTED] ha scritto:
I think you need to explain what kind of SELECTs you want to do, and
what
results you expect.
you're right, I'll try to explain it better
I'm working on a system that must keep track of all the music
broadcasted by a tv,
so, let's
My answers interspersed below (and yes, I have read his follow up reply
that had additional information)
Giulio [EMAIL PROTECTED] wrote on 10/11/2004 05:44:43 AM:
Hi all,
I have some doubts about how to implement this kind of scenario:
I have a table of elements in cronological order,
I have some data that is stored by the year it is related to. So I have one
table that stores the Year the data is related to, among other things. At any
given time, 1 year is considered the 'active year', and the rest are
considered inactive.
The table is something like:
CREATE TABLE
I've got a history table that performs a similar function. except in my
case I can have more than 1 active row. I put in an is_active column
and defined the type as a bool. an enum is actually a String in mysql,
which i didn't want to deal with. This table has only a few thousand
rows, so
EB My thought was to add a new field to the listings table that would
EB contain a comma-separated list of CategoryIDs, but something doesn't
EB feel right about this solution.
This would break the first normalization form and is extremely bad
Okay - I thought something was off...
First of
You are right, a comma separated list won't work since you won't be
able to do joins on it. To create a one to many relation, you actually
need to create another table to hold the relation.
CREATE TABLE listCatLink (
ListingID bigint(20) unsigned NOT NULL,
CategoryID int(11) NOT NULL
)
On Aug
As posted, your data structure supports two one-to-many relationships, not
the one-to-one relationships as you described. You can have multiple
Listings per Category and multiple Categories per Group. What it sounds
like you have been asked to do is to support a many-to-many relationship.
You
!
-Erich-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 11:51 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Design Question
As posted, your data structure supports two one-to-many relationships,
not
the one-to-one
] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 11:51 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Design Question
As posted, your data structure supports two one-to-many relationships,
not
the one-to-one relationships as you described. You can have multiple
Listings
Justin French [EMAIL PROTECTED] wrote:
Should I worry at 40,000? 100,000? Or will the indexing of the siteID
keep everything extensible?
Indexing is designed to keep SELECT speed small with no matter how much data it
is. You should ensure that the siteID index is properly used (use EXPLAIN
Hi all,
I'm in the planning phase of a hosted web application where all
instances of the app (a sort-of website CMS) will be running off a
single code source. I've got a clear picture about everything except
for the database design.
a) I could have a separate database table structure for
Hi all, I am having a little trouble deciding how to relate some of my
tables together.
I was wondering about creating one big lookup table to relate 3 or 4
tables together, but wasn't sure if that was a good id, or should I have
a look up table
For each pair of tables.
Here is a simple
To simplify, is It better to have many smaller lookup tables or one big
one?
Traylor:
You can create three entity tables (organization,contact,event) + the relation
tables (org_contact, org_event, contact_event). Small lookup tables are usually
better, and also give you points for sticking
On Thu, 2004-05-20 at 07:13, Lewick, Taylor wrote:
Hi all, I am having a little trouble deciding how to relate some of my
tables together.
I was wondering about creating one big lookup table to relate 3 or 4
tables together, but wasn't sure if that was a good id, or should I have
a
Hi,
I'm writing a database for an online candle store. Here's the situation. This store
sells all sorts of items including candles. Now the gist is that some of the candles
can be made in different types of waxes and some only have one wax. My question is
how do I resolve this when I write
JOHN MEYER [EMAIL PROTECTED] wrote on 07/04/2004 15:39:10:
Hi,
I'm writing a database for an online candle store. Here's the
situation. This store sells all sorts of items including candles.
Now the gist is that some of the candles can be made in different
types of waxes and some
Everything I've read about creating online stores is that you are
selling inventory items, not the items that makeup the inventory item.
So if you sell a red candle made from wax X, candle is the product and
red wax X are two attributes of the product.
Ideally your structure would work for any
design question
Hi,
I'm writing a database for an online candle store. Here's the situation.
This store sells all sorts of items including candles. Now the gist is that
some of the candles can be made in different types of waxes and some only
have one wax. My question is how do I resolve this when
What are the advantages and disadvantages of using multiple databases, versus
placing all tables in one uber-database?
I understand and appreciate the organizational value of multiple databases,
but what other issues are involved?
I ask this because I'm considering moving from tables across
) and scalability pov too, to split
it up into multiple databases.
Thanks,
Matt
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of TO
Sent: 21 March 2004 15:14
To: [EMAIL PROTECTED]
Subject: multiple databases: design question
What are the advantages and disadvantages
I have ip_address and ports that I want to use in my table. I was just going to
make each one a varchar. But was wondering if anyone has a better suggestion?
Should I use int for ports, which will have an index. Not sure how to store
ip_address.
This table has the possibility of having 800
rmck said:
I have ip_address and ports that I want to use in my table. I
was just going to make each one a varchar. But was wondering if
anyone has a better suggestion?
PostgreSQL ;-)
It has a native datatype for storing IP addresses. That means that
things like sorting and subnet inclusion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jochem van Dieten wrote:
rmck said:
I have ip_address and ports that I want to use in my table. I
was just going to make each one a varchar. But was wondering if
anyone has a better suggestion?
PostgreSQL ;-)
It has a native datatype for
Mark Matthews wrote:
Jochem van Dieten wrote:
rmck said:
I have ip_address and ports that I want to use in my table. I
was just going to make each one a varchar. But was wondering if
anyone has a better suggestion?
PostgreSQL ;-)
It has a native datatype for storing IP addresses. That means that
rmck wrote:
I have ip_address and ports that I want to use in my table. I was just going to make each one a varchar. But was wondering if anyone has a better suggestion?
Should I use int for ports, which will have an index. Not sure how to store ip_address.
Use a varchar for the IP address.
I have a contract that has about 6 fields that need to be filled out each time it is
signed. My goal is to have a form that only asks for the missing information then
includes that into the contract which is then printed and then stored in a database
completed. There would be 3 unique things
That worked like a charm, thanks so much! I don't know why I didn't try
that before!
Julian
At 02:46 PM 11/21/2003 -0600, Paul DuBois wrote:
At 10:56 -0500 11/21/03, Julian Zottl wrote:
Andy,
Thanks for responding. I think that I am going to go with the idea of
creating a tale for each day.
Wouldn't this also work?:
mysql -u root -p -e CREATE TABLE t$date(...) yourdatabase
-Original Message-
From: Paul DuBois [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 12:46 PM
To: Julian Zottl; Andy Eastham; Mysql List
Subject: RE: DB design question - shell scripting
: DB design question - shell scripting...
At 10:56 -0500 11/21/03, Julian Zottl wrote:
Andy,
Thanks for responding. I think that I am going to go with the idea
of creating a tale for each day. My thoughts were to write a shell
script to do this for me, but I am running into a problem: I wrote
Hello all,
I am designing a database right now that will have between 300-400k inserts
per day. I need to keep this information for approximately 3 months and
will probably do 5-10 reads on the data set per day. I've been storing it
in one table up to now (only col.), but the searches are
]
Subject: DB design question
Hello all,
I am designing a database right now that will have between
300-400k inserts
per day. I need to keep this information for approximately 3 months and
will probably do 5-10 reads on the data set per day. I've been
storing it
in one table up to now (only col
the earliest or
latest available table, and if so, modify the union so that you don't try to
search a non-existent table.
Hope this helps,
Andy
-Original Message-
From: Julian Zottl [mailto:[EMAIL PROTECTED]
Sent: 21 November 2003 12:03
To: [EMAIL PROTECTED]
Subject: DB design question
]
To: Andy Eastham [EMAIL PROTECTED]; Mysql List
[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 7:56 AM
Subject: RE: DB design question - shell scripting...
Andy,
Thanks for responding. I think that I am going to go with the idea of
creating a tale for each day. My thoughts were to write a shell
At 10:56 -0500 11/21/03, Julian Zottl wrote:
Andy,
Thanks for responding. I think that I am going to go with the idea
of creating a tale for each day. My thoughts were to write a shell
script to do this for me, but I am running into a problem: I wrote
the following:
#!/bin/sh
date=`date
Message-
From: James Walters [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 9:42 AM
To: [EMAIL PROTECTED]
Subject: Basic Database Design Question
Hello,
DB novice checking in here with a basic design
question. I have a table called 'nms_apps' which
stores information about
Hello,
DB novice checking in here with a basic design
question. I have a table called 'nms_apps' which
stores information about all of our applications which
we have developed/maintained for our client. One
column which I would like to use is called 'used_by',
which would store information
Phone/fax: (408) 904-7198
[EMAIL PROTECTED]
-Original Message-
From: James Walters [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 10:42 AM
To: [EMAIL PROTECTED]
Subject: Basic Database Design Question
Hello,
DB novice checking in here with a basic design
question. I
29, 2003 9:42 AM
To: [EMAIL PROTECTED]
Subject: Basic Database Design Question
Hello,
DB novice checking in here with a basic design
question. I have a table called 'nms_apps' which
stores information about all of our applications which
we have developed/maintained for our client. One
column
Hello... I am currently working on a User Account Management
system. I am actually a Unix SA who is moonlighting at work as a MySQL
DBA and web developer. I am learning a lot and enjoying the work, but I am
severely lacking in database design fundamentals. I have created a couple
very
[snip]
Let's say that I have users Mary, Joe, Frank, and Dan. I also have
servers panther, cheetah, jaguar and lion. The data for each account that I
want to maintain is UID, GID, home directory, and default shell.
In designing a table or tables to handle this example what can I
make as a
On 18-Jun-2003 NIPP, SCOTT V (SBCSI) wrote:
Hello... I am currently working on a User Account Management
system. I am actually a Unix SA who is moonlighting at work as a MySQL
DBA and web developer. I am learning a lot and enjoying the work, but I
am
severely lacking in database
| user_id | Marks | Now I have an other table where I keep the name
etc.. from each user. You will all kill me for this, but in access you
could the setup a relation between user_id and the id of the user in the
user table. Is something like that possible in mysql ?
So that if I select some
-Original Message-
From: Jonas Geiregat [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2003 9:55 AM
To: [EMAIL PROTECTED]
Subject: mysql design question ?
| user_id | Marks | Now I have an other table where I keep the name
etc.. from each user. You will all kill me for this, but in access you
Dear all,
I'm designing a database for a travel company but i'm puzzled.. Maybe you can shed a
light on this:
I've got an travelpackage that can exicts of more possible departure date's but it has
also have more than one accommodation.
So 3 tables:
(table one)
-Travelpackageid (Primary Key)
I am fairly new to this, so please bare with me on this.
I am designing a database that stores information about the computers I
manage, and am developing a PHP front end to add, view, and edit information
about the computers. One issue I ran into is designing the hard drive
information. Some
Hi,
I have a design question for mysql database that I am wanting to create a
my movies collection. I was going to do as one-to-one database, but I see
now that I need to do as a one-to-many. I have never done a one-to-many but
I see that is the way to go.
I guess then is can someone show me
I would like to set up a MySql database that will
store distance information for a milage lookup
program. The user will enter the origin city and the
destination city for some predefined trips. Then the
query will need to return the milage broken down by
state. For example, for an origin city
Hi all,
I am in the process of designing a MySQL database that will run on Redhat
7.1, but I am fairly sketchy on MySQL and performance.
What I want to do is have a database that keeps track of large distribution
lists. Each list has a unique ID, an owner (which is a reference to an ID in
On 3/28/02 1:39 PM [EMAIL PROTECTED] wrote:
What I want to do is have a database that keeps track of large distribution
lists. Each list has a unique ID, an owner (which is a reference to an ID in
another table) and a creation date.
My question is this: Would it be more efficient to have
-Original Message-
From: Ben Holness [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
...
My question is this: Would it be more efficient to have each entry in the
list stored in this table in the database, or would I be better
off having a
reference to a file that is
Hi Ben:
Performance would definitely be better if you store the data in the
database as opposed to simply storing references to files. Sounds like you
could solve this with 2 tables with one for the actual lists (assuming the
structure of all your list is the same) and the other for the list
Hi Chris/Nick/Scalper,
Thanks for the replies. I am not too sure how to implement this in tables,
so I will give an example:
Let's say I have three lists - a,b and c. List a contains 10,000 entries,
list b contains 2,500 entries and list c contains 75,000 entries.
I have a table of lists, with
1 - 100 of 126 matches
Mail list logo
