|
|
Posted by Jerry Stuckle on 10/07/07 19:56
macca wrote:
>> The most stoopid argument I've seen in this group in ages.
>> The question was about how to do something in SQL. The answer was how
>> to do it in SQL.
>
>> Wrapping some stupid shit like this around it does not make it a PHP
>> question.
>
>
>
> Actually, yes it does. the OP wanted to know how to format the SQL
> tsatement AND output the results, which unless I'm mistaken (which I'm
> not) would be done with php.
>
>
The answer had nothing to do with PHP. It was strictly a SQL response.
>
>> Many of us want to keep this according to the charter - and not make it
>> a group for any question under the sun.
>
>
> I would hardly call a php/MySQL question "any question under the sun"
>
So where are you going to draw the line?
>
>> Unfortunately, there are a few idiots here who don't seen to understand
>> that. They need to stroke their egos by answering off-topic questions
>> instead of gently directing people to a more appropriate newsgroup.
>
>
> It is not idiotic to help someone. That is partly what these
> newsgroups are for. Nor does it have anything to do with "egos" and if
> answering questions in newsgroups is just to stroke your ego then you
> are doing it for the wrong reason.
>
It is idiotic not to direct someone to a more appropriate newsgroup
where they can get better answers for their questions.
>
>> For questions like this, comp.databases.mysql is much more appropriate.
>> They have *real* SQL experts hanging out there, not that wanna-be's we
>> see answering SQL questions here. And people who as questions will be
>> much better served by asking their SQL questions over there.
>
>
> Maybe so, but what if you dont know what would be down to SQL and what
> would be down to php? where would you ask? As the question obviously
> involves both, here is a good a place as any.
>
Ask by cross-posting to both newsgroups. Or accept a response that a
MySQL newsgroup would be a better place to ask, then ask over there.
>
>> Oh, and one other thing.
>
>> MySQL and PHP are not closely linked. They are only in the minds of
>> some programmers. MySQL is used with a lot of other languages. And PHP
>> uses a lot of other databases.
>
>> There is *NOTHING* closely linked about PHP and MySQL except a lot of
>> people use both products.
>
>
> PHP and MySQL ARE closely linked in many ways. With PHP being the most
> popular Open Source scripting language in the world, and MySQL being
> the most popular Open Source RDBMS in the world, they are the most
> likely combination when using PHP, and well documented in many LAMP
> and php/mysql books and websites.
>
Only in your mind. PHP is a programming language. MySQL is a database.
PHP can access MySQL - as it can PostGres, SQL Server, Access, Oracle,
DB2... So according to your theory, how to configure SQL Server is
also applicable here, because it can be accessed with PHP.
> I did not say that they were EXCLUSIVELY RELATED, but they ARE closely
> linked, with a myriad of specific MySQL functions built into php.
>
No more so than PHP is linked with any of the other databases noted
above, or indeed, many other products. And MySQL is no more closely
linked with PHP than it is with any other language.
>
> Anyway, I cant help but think you are getting too wound up about this.
> It was a simple question with a simple answer which any in-the-know
> php/sql developer could answer with ease , and did in this case by
> helpful people like Shelly and myself.
>
> Why people like you have to then come along ranting and raving and
> swearing, even after the question has been answered is beyond me.
>
Because some of us are tired of people encouraging off-topic questions
in this newsgroup.
Get it in your mind. This is comp.lang.php, not
comp.something.php-mysql. There is also a comp.databases.mysql.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|