Re: forum vs email

2014-12-10 Thread Reindl Harald


Am 10.12.2014 um 18:38 schrieb h...@tbbs.net:

2014/12/10 09:00 +0100, Johan De Meersman 

 One of the (for me, at least) defining features of a forum, is that the 
subjects tend to be divided up into a tree structure, which has it's own 
benefits 

Something more sophisticated than grouping messages by trimmed subject-lines?
maybe involving such header lines as were used in the old netnews (if e-mail is 
part of it)?


every sane MUA supports threading
see attached screenshot

maybe if you switch to such one it also could quote properly



signature.asc
Description: OpenPGP digital signature


Re: forum vs email

2014-12-10 Thread hsv
 2014/12/10 09:00 +0100, Johan De Meersman 
 One of the (for me, at least) defining features of a forum, is that the 
subjects tend to be divided up into a tree structure, which has it's own 
benefits  

Something more sophisticated than grouping messages by trimmed subject-lines?
maybe involving such header lines as were used in the old netnews (if e-mail is 
part of it)?


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



Re: signal handling in mysql cli

2014-12-10 Thread Johan De Meersman
- Original Message -
> From: "Sebastien FLAESCH" 
> Subject: Re: signal handling in mysql cli

> Nobody concerned by this case?
> Simple question: is it safe or not to do a KILL QUERY in a SIGINT signal
> handler?

I don't see what the extra risk would be as opposed to doing so in any other 
thread of your code, or in another program entirely. As long as you're sure 
about which particular query you're shooting in the face, it should be 
perfectly fine.


-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

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



Re: signal handling in mysql cli

2014-12-10 Thread Sebastien FLAESCH

Nobody concerned by this case?
Simple question: is it safe or not to do a KILL QUERY in a SIGINT signal 
handler?
S.

On 12/03/2014 05:25 PM, Sebastien FLAESCH wrote:

Hi all,

I have a similar question regarding KILL QUERY usage:

We have a C client program using libmysqlclient.so, it is a single-threaded 
program.

When running a long query, how can I send the KILL QUERY command when a SIGINT 
(CTRL-C)
is caught? (of course we implement a signal handler, so we keep the control)

=> Is is safe to establish a new connection to the server in the signal 
handler, using
mysql_init() + mysql_real_connect(), and execute the KILL QUERY with the mysql 
thread
id I got from the initial mysql_init() / mysql_real_connect()?

I made some tests, and it seems to work fine, the long query returns SQL error 
-1317:
"Query execution was interrupted" (which is expected)

We want to support SQL interruption properly, so please someone from the dev 
team,
give me a clear answer... I don't want to use a side effect or undocumented 
feature.

Doing all this stuff in a signal handler is certainly risky... no?

I could not find the information in the documentation (mysql_real_connect).

I wish there would be an API like mysql_cancel_query(), similar to Oracle's OCI
OCIBreak().

Thanks!
Seb



On 12/02/2014 05:13 PM, walter harms wrote:

hi list,

when i use CTRL-C to break a query that works fine in interactive mode.

mysql> select sleep(10) ;
^CCtrl-C -- sending "KILL QUERY 24289" to server ...
Ctrl-C -- query aborted.
+---+
| sleep(10) |
+---+
+---+
1 row in set (0.86 sec)

but when i use the noninteractive mode
   timeout 5 mysql -BAN -e "select now(); select sleep (100) ; select now() "

i looks like that  but "show full processlist;" shows otherwise and that is true
as a list of long running querys showed.

Is there a way to make it behave like the interactive version ?
Now it is a bit confusing for everyone.

re,
  wh







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



Re: forum vs email [was: Re: table-for-column]

2014-12-10 Thread Jigal van Hemert

Hi,

On 10/12/2014 10:09, Johan De Meersman wrote:
Hm. Typo3 is a CMS; I take it the integration you're speaking of is 
specific to their support environment, and not part of the CMS? 


Correct, TYPO3 is a CMS (also FOSS GPL2+) and the integration is indeed 
not part of the CMS. See my other reply for details on the software that 
was used.


--
Met vriendelijke groet,

Jigal van Hemert.


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



Re: forum vs email [was: Re: table-for-column]

2014-12-10 Thread Jigal van Hemert

Hi,

On 10/12/2014 09:02, Johan De Meersman wrote:

- Original Message -

From: "Jigal van Hemert" 
Subject: Re: forum vs email [was: Re: table-for-column]

On typo3.org there used to be mailing lists only in a distant past.
Later on newsgroups were set up which communicate with the mailing lists
(newsgroups are the central source of messages).
Rather recently a forum was built on top of the newsgroup data (FUD
forum was used). Users on all three message sources can easily
communicate with eachother.

Hmm. That sounds interesting, I'll have a look. I don't suppose the software is 
available under a foss license? :-p


Mailing lists [1] themselves use Mailman [2] (GPL), forum [3] is done 
with FUD forum [4] (FOSS GPL2), for integration between mailing lists 
and newsgroups, please contact the TYPO3 server admin team [5]. I'm sure 
they will tell you all you want to know about this setup.


[1] http://lists.typo3.org/cgi-bin/mailman/listinfo
[2] http://www.gnu.org/software/mailman/
[3] http://forum.typo3.org/
[4] http://cvs.prohost.org/index.php
[5] http://typo3.org/teams/server-team/

-- Met vriendelijke groet, Jigal van Hemert.

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



Re: forum vs email [was: Re: table-for-column]

2014-12-10 Thread Johan De Meersman
- Original Message -
> From: "Johan De Meersman" 
> Sent: Wednesday, 10 December, 2014 09:02:45
> Subject: Re: forum vs email [was: Re: table-for-column]

> Hmm. That sounds interesting, I'll have a look. I don't suppose the software 
> is
> available under a foss license? :-p

Hm. Typo3 is a CMS; I take it the integration you're speaking of is specific to 
their support environment, and not part of the CMS?


-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

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



Re: forum vs email [was: Re: table-for-column]

2014-12-10 Thread Johan De Meersman


- Original Message -
> From: "Jigal van Hemert" 
> Subject: Re: forum vs email [was: Re: table-for-column]
> 
> On typo3.org there used to be mailing lists only in a distant past.
> Later on newsgroups were set up which communicate with the mailing lists
> (newsgroups are the central source of messages).
> Rather recently a forum was built on top of the newsgroup data (FUD
> forum was used). Users on all three message sources can easily
> communicate with eachother.

Hmm. That sounds interesting, I'll have a look. I don't suppose the software is 
available under a foss license? :-p


-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

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



Re: forum vs email

2014-12-10 Thread Johan De Meersman
- Original Message -
> From: "Sándor Halász" 
> Subject: Re: forum vs email

> I believ that one could both by e-mail and through a webbrowser comment on a
> Google group.

True; and before that there was yahoo groups, and others. Those are not fora, 
however, merely web interfaces to mailing lists / newsgroups. One of the (for 
me, at least) defining features of a forum, is that the subjects tend to be 
divided up into a tree structure, which has it's own benefits; although as 
Shawn says, there is also benefit to the broad exposure you get on a mailing 
list.


> And one who reads & sends e-mail through a webbrowser surely considers
> discussion through e-mail simplie more overhead than using his webbrowser for

I use webmail - to the point where I host my own domains. Still vastly prefer 
email over fora, as interfaces go. Better read/unread views, proper filtering, 
sorting stuff into folder structures that are convenient for me instead of for 
the administrator, etc.


> discussion, too. I further suspect e-mail clients on own computers are not in
> fashion.

That does seem to be the case; although I think in a corporate setting the 
situation is different.


-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

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