Re: Bad database design can cause unnecessary coding

Path	csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	"J.O. Aho" <user@example.net>
Newsgroups	comp.lang.php, alt.php.sql
Subject	Re: Bad database design can cause unnecessary coding
Date	Sun, 04 Nov 2012 16:45:28 +0100
Lines	63
Message-ID	<afngsoFq6n1U1@mid.individual.net> (permalink)
References	<cnKks.137076$Tf3.11521@fx12.am4> <k708e6$fjt$1@dont-email.me> <k70b4q$2p7$1@news.metronet.hr> <k70buo$2bo$1@dont-email.me> <Ps5ls.150479$Xv.123477@fx07.am4> <afk82dF3gokU1@mid.individual.net> <F9rls.105960$YJ1.81669@fx09.am4>
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	individual.net o72Gk10Pzh80rsG6wxFPyw/QgUZfRPvdBijJXpot4+rVTDkDgWni1ukT5S0eauOnLt
Cancel-Lock	sha1:U4H20EaNOC1ZL6o21qe0IT/5eXI=
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120923 Thunderbird/15.0.1
In-Reply-To	<F9rls.105960$YJ1.81669@fx09.am4>
Xref	csiph.com comp.lang.php:7457

Cross-posted to 2 groups.

Show key headers only | View raw

On 04/11/12 11:09, Tony Marston wrote:
> "J.O. Aho"  wrote in message news:afk82dF3gokU1@mid.individual.net...
>>
>> On 03/11/12 10:28, Tony Marston wrote:
>>
>>> It *IS* a PHP topic for the simple reason that almost every PHP program
>>> accesses a database, and most databases are designed by the programmer
>>> him/herself.
>>
>> I have to agree with Jerry that it's off topic in this news group, it
>> had been more on topic at alt.php.sql.
>
> Are you saying that it is forbidden to post anything related to SQL on
> this newsgroup? What about HTML? CSS? JavaScript?

Yes, HTML, CSS and JavaScript are also off topic here, as they don't 
have anything to do with the PHP. Try to see the different usergroups as 
sorting mail, you don't mix your business mail with your private, as it 
makes it easier to find the right mail when you are looking for a mail 
from a friend with his vacation photos.

For this reason a post in comp.lang.php may be on-topic, while it's 
off-topic in alt.php.sql (and the other way too) and there are times 
when a post can be on-topic on both or none. It's up to the poster to 
keep it on-topic and promoting a site is in general off-topic on most 
usergroups.

>> Something that people dislike here and most other usergroups is that
>> promotion of your own site and most of the time it's done in a
>> usergroup it's quite low quality or even requiring payment to access
>> the low quality information.
>
> I pointed to a separate article for the simple reason that it was too
> large to post here. I was not saying "please visit my site which
> contains lots of stuff".

You kind of did that, as you started a new thread and promoted your site 
(article), it had been a lot different if there had been someone asking 
how to make a good database design on a database related usergroup, then 
you could have posted your link and said here you can read some stuff I 
have discovered.

>> A better way to do is to start a discussion and show your skills in
>> there without promoting a website of self-interest.
>
> If you can't be bothered to read the article and respond intelligently
> to the points raised in it then don't respond at all.

You didn't post to increase the number of visitors to IBMs "Approach's 
database design and how to use a relational database", but to your own 
site and in the completely wrong usergroup.

I'm not replying to your articles content, but trying to explain why 
people dislike what you did.

-- 

  //Aho

Thread

Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-02 07:12 +0000
  Re: Bad database design can cause unnecessary coding "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-11-02 09:53 +0100
    Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-03 09:14 +0000
      Re: Bad database design can cause unnecessary coding "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-11-03 18:01 +0100
        Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-03 15:03 -0400
        Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-04 10:11 +0000
          Re: Bad database design can cause unnecessary coding "Peter H. Coffin" <hellsop@ninehells.com> - 2012-11-04 14:37 -0600
      Re: Bad database design can cause unnecessary coding "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-11-03 19:00 +0100
        Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-04 10:18 +0000
          Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-04 07:29 -0500
  Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-02 06:48 -0400
    Re: Bad database design can cause unnecessary coding Goran <goran@nospam.com> - 2012-11-02 12:34 +0100
      Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-02 07:48 -0400
        Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-03 09:28 +0000
          Re: Bad database design can cause unnecessary coding "J.O. Aho" <user@example.net> - 2012-11-03 10:56 +0100
            Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-04 10:09 +0000
              Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-04 07:32 -0500
              Re: Bad database design can cause unnecessary coding "J.O. Aho" <user@example.net> - 2012-11-04 16:45 +0100
          Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-03 10:52 -0400
      Re: Bad database design can cause unnecessary coding The Natural Philosopher <tnp@invalid.invalid> - 2012-11-02 11:56 +0000
    Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-03 09:17 +0000
      Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-03 10:54 -0400
        Re: Bad database design can cause unnecessary coding Luuk <luuk@invalid.lan> - 2012-11-03 16:06 +0100
          Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-03 11:25 -0400
  Re: Bad database design can cause unnecessary coding Denis McMahon <denismfmcmahon@gmail.com> - 2012-11-02 11:13 +0000
    Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-03 09:31 +0000
      Re: Bad database design can cause unnecessary coding Denis McMahon <denismfmcmahon@gmail.com> - 2012-11-03 13:08 +0000
        Re: Bad database design can cause unnecessary coding Jerry Stuckle <jstucklex@attglobal.net> - 2012-11-03 10:55 -0400
        Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-04 10:04 +0000
  Re: Bad database design can cause unnecessary coding Luuk <luuk@invalid.lan> - 2012-11-03 11:04 +0100
    Re: Bad database design can cause unnecessary coding "Tony Marston" <TonyMarston@hotmail.com> - 2012-11-04 10:30 +0000
  Re: Bad database design can cause unnecessary coding Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-11-15 15:49 +0100
    Re: Bad database design can cause unnecessary coding "Peter H. Coffin" <hellsop@ninehells.com> - 2012-11-15 12:03 -0600

csiph-web