Yes that's right, until now I didn't spent time on writing another table
because my job was to develop some internal system to manage the company
projects & HR (we are too small, it won't make the difference).
Well umm thanks, I'm going to write the blueprints for the tables :P
On Fri, Jan 30, 20
On Fri, Jan 30, 2009 at 8:37 AM, Andrew Ballard wrote:
> On Fri, Jan 30, 2009 at 3:38 AM, Nitsan Bin-Nun
> wrote:
> > Hi there,
> >
> > I'm working on something similar to mailing list in which every
> registered
> > user has the ability to create a mailing list and join others mailing
> lists.
On Fri, Jan 30, 2009 at 3:38 AM, Nitsan Bin-Nun wrote:
> Hi there,
>
> I'm working on something similar to mailing list in which every registered
> user has the ability to create a mailing list and join others mailing lists.
>
> My users table is something like that (in short):
>
> CREATE TABLE IF
> I have thought of using comma-separated ID's in special field in the lists
> table of the users who have joined that specific list, but I have also
> thought of doing the same at the users table, then I had another solution
> which is to create new table:
>
> create table `relations` (
> `listid
2009/1/30 Nitsan Bin-Nun
> Hi there,
>
> I'm working on something similar to mailing list in which every registered
> user has the ability to create a mailing list and join others mailing
> lists.
>
> My users table is something like that (in short):
>
> CREATE TABLE IF NOT EXISTS `users` (
>
Hi there,
I'm working on something similar to mailing list in which every registered
user has the ability to create a mailing list and join others mailing lists.
My users table is something like that (in short):
CREATE TABLE IF NOT EXISTS `users` (
`id` INT( 11 ) UNSIGNED NOT NULL AUTO_INCRE
6 matches
Mail list logo
