Wayne,
Yes, you have characterized it pretty well. Additionally, it will be
accessed typically by maybe a dozen individuals, typically only reading
information from the database and infrequently writing to it.
--Bill
On Sun, Dec 12, 2010 at 7:36 AM, Wayne Werner wrote:
>
>
> I think the large
On Sat, Dec 11, 2010 at 12:07 PM, Bill Allen wrote:
> David,
>
> Thanks for the feedback. I should have been more specific on the usage of
> the data. The data will be some email addresses, names, department, and an
> indicator if the email address is internal to the business or an external
>
David,
Thanks for the feedback. I should have been more specific on the usage of
the data. The data will be some email addresses, names, department, and an
indicator if the email address is internal to the business or an external
contact. So, one table with these being the fields in each rec
On Fri, Dec 10, 2010 at 10:23 PM, Bill Allen wrote:
> This is somewhat non-Python specific I have an idea for a Python
> application that I want to write at work. The application needs to have a
> data file be available to multiple users for access, read and write. I
> know that a typical dat
This is somewhat non-Python specific I have an idea for a Python
application that I want to write at work. The application needs to have a
data file be available to multiple users for access, read and write. I
know that a typical database, such as mysql, would work ok. However, I am
trying t
