Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #12753
| From | "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: login validation from 2 tables in same database |
| Date | 2014-02-03 13:18 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <lco4v1$a05$1@dont-email.me> (permalink) |
| References | <JYudncI3ia_9xnLPnZ2dnUVZ_sOdnZ2d@giganews.com> <lco35a$vog$1@dont-email.me> |
Denis McMahon wrote: > hujan wrote: >> Also, each table have different number of columns. Below is my table >> fields: >> >> user [id(PK), profile, name, gender, dob, contact, addr1, >> email,username, password] >> >> student [reg_no(pk), s_name, s_gender, s_ic, s_dob, s_contact, s_email, >> s_addr1, s_addr2, country, s_dept, s_post, username, password] > > Your data needs some normalisation. If a student is also a user you're > storing a lot of duplicated data. Not only that: I would recommend also breaking up the name fields to firstname, mi, lastname and adding city, state, postcode fields. Otherwise, the "combined" fields are quite useless for searching. Data gatherers will use: [John Smith] or [Smith, John A.] if you give 'em a chance... -- -bts -This space for rent, but the price is high
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
login validation from 2 tables in same database hujan <zarinsung@hotmail.com> - 2014-02-03 03:03 -0600
Re: login validation from 2 tables in same database Denis McMahon <denismfmcmahon@gmail.com> - 2014-02-03 12:47 +0000
Re: login validation from 2 tables in same database "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> - 2014-02-03 13:18 +0000
Re: login validation from 2 tables in same database Denis McMahon <denismfmcmahon@gmail.com> - 2014-02-03 23:13 +0000
csiph-web