From: fatblokeonbike [mailto:[EMAIL PROTECTED]

> .
> Dear List,
> 
> My thanks to those who replied.
> 
> I'm embarrassed as anything - the bloke I'm doing this thing 
> for has now changed his tiny mind and has decided to have a 
> set number of images per property, whereas before he was 
> contemplating accepting a widely variable number.  I can thus 
> stick all the fields in the one table and, with that, my need 
> for Joins goes west.  While this now needs loads'v table 
> reconstruction, at least I'm well able in that area.
> 
> Thanx again for your assistance and offers of assistance.


Damn, I was really hoping to get to the bottom of the problem. Ah well.

FYI, might I suggest going with your original design anyway? If this guy changes his 
mind like this often, then he may very well decide, a month after launch, that he 
wants to go back to a variable # of images per property. In that case you'd be right 
back at the drawing board. If you build it that flexible from day one, though, he can 
change his mind to his heart's content.

Anyway, good luck!


-- 
Mike Johnson
Web Developer/Systems Asst.
Smarter Living, Inc.
phone (617) 497-2500 x226

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to