Re: [RDBO] Best way to do multiple calls to database

2007-03-28 Thread James Masters
Thanks for your very helpful reply, Jonathan. It answered my general question but I'm left with a couple of more specific ones. Pl. see in line. > I do that with ~20 tables that hold data I consider 'constants'. If > this data is unchanging, there's no need to continually hit the db. > ( note,

Re: [RDBO] Rose::DB::Loader (aka feeling dim)

2007-03-28 Thread Adrian Howard
On 28 Mar 2007, at 15:12, John Siracusa wrote: > On 3/28/07, Adrian Howard <[EMAIL PROTECTED]> wrote: >> CREATE TABLE products ( >> id SERIAL NOT NULL PRIMARY KEY, >> nameVARCHAR(255) NOT NULL, >> vendor_id INT REFERENCES vendors (id), >> UNIQUE(

Re: [RDBO] Rose::DB::Loader (aka feeling dim)

2007-03-28 Thread Peter Karman
John Siracusa scribbled on 3/28/07 9:12 AM: > On 3/28/07, Adrian Howard <[EMAIL PROTECTED]> wrote: >> CREATE TABLE products ( >> id SERIAL NOT NULL PRIMARY KEY, >> nameVARCHAR(255) NOT NULL, >> vendor_id INT REFERENCES vendors (id), >> UNIQUE(nam

Re: [RDBO] Rose::DB::Loader (aka feeling dim)

2007-03-28 Thread John Siracusa
On 3/28/07, Adrian Howard <[EMAIL PROTECTED]> wrote: > CREATE TABLE products ( > id SERIAL NOT NULL PRIMARY KEY, > nameVARCHAR(255) NOT NULL, > vendor_id INT REFERENCES vendors (id), > UNIQUE(name) > ) TYPE = InnoDB; While it will happily acc

[RDBO] Rose::DB::Loader (aka feeling dim)

2007-03-28 Thread Adrian Howard
Okay. This is probably me being exceptionally stupid but with MySQL 5.0.22 (I know...) with this schema: DROP TABLE IF EXISTS vendors; CREATE TABLE vendors ( idSERIAL NOT NULL PRIMARY KEY, name VARCHAR(255) NOT NULL, UNIQUE(name) ) TYPE = InnoDB