13 Oct
2004
13 Oct
'04
10:12 p.m.
Hi all
please look at bug #1042521 [1]. The problem there is that MySQL wants unix
end of lines, while it is running on Mac. Easiest solution would be to change
PMA_whichCrlf to return \n for mac. As I see other places, there is anyway
code like: (PMA_whichCrlf() == "\n") ? '\n' : '\r\n'), which
means we didn't
use \r on any other place than export (and this code was probably wrong for
Mac). Is it okay to do this change?
1.
https://sourceforge.net/tracker/index.php?func=detail&aid=1042521&g…
--
Michal Čihař | http://cihar.com
14 Oct
14 Oct
8:48 a.m.
Michal C(ihar( a écrit:
Hi all
please look at bug #1042521 [1]. The problem there is that MySQL wants unix
end of lines, while it is running on Mac. Easiest solution would be to change
PMA_whichCrlf to return \n for mac. As I see other places, there is anyway
code like: (PMA_whichCrlf() == "\n") ? '\n' : '\r\n'), which
means we didn't
use \r on any other place than export (and this code was probably wrong for
Mac). Is it okay to do this change?
1.
https://sourceforge.net/tracker/index.php?func=detail&aid=1042521&g…
Hi Michal,
was this message sent before the last comment from Ryan?
Marc
8:53 a.m.
On Thu 14. 10. 2004 20:47, Marc Delisle wrote:
Michal C(ihar( a écrit:
Yes, I already thought about this situation, but didn't mention it. We should
probably use eol according to server and not according to client.
--
Michal Čihař | http://cihar.com
Hi all
please look at bug #1042521 [1]. The problem there is that MySQL wants
unix end of lines, while it is running on Mac. Easiest solution would be
to change PMA_whichCrlf to return \n for mac. As I see other places,
there is anyway code like: (PMA_whichCrlf() == "\n") ? '\n' :
'\r\n'),
which means we didn't use \r on any other place than export (and this
code was probably wrong for Mac). Is it okay to do this change?
1.
https://sourceforge.net/tracker/index.php?func=detail&aid=1042521&g…
d=23067&atid=377408
Hi Michal,
was this message sent before the last comment from Ryan?
9:06 a.m.
Michal C(ihar( a écrit:
On Thu 14. 10. 2004 20:47, Marc Delisle wrote:
Ryan, on 2004-10-14, 09:15, talks about inconsistency for the eol during a single
export, between the CREATE TABLE and the lines of the extended inserts.
I did not check this myself.
What about asking the user with an option, the eol style he wants?
Marc
Michal C(ihar( a écrit:
Yes, I already thought about this situation, but didn't mention it. We should
probably use eol according to server and not according to client. Hi all
please look at bug #1042521 [1]. The problem there is that MySQL wants
unix end of lines, while it is running on Mac. Easiest solution would be
to change PMA_whichCrlf to return \n for mac. As I see other places,
there is anyway code like: (PMA_whichCrlf() == "\n") ? '\n' :
'\r\n'),
which means we didn't use \r on any other place than export (and this
code was probably wrong for Mac). Is it okay to do this change?
1.
https://sourceforge.net/tracker/index.php?func=detail&aid=1042521&g…
d=23067&atid=377408
Hi Michal,
was this message sent before the last comment from Ryan?
9:15 a.m.
On Thu 14. 10. 2004 21:05, Marc Delisle wrote:
Ryan, on 2004-10-14, 09:15, talks about inconsistency
for the eol during a
single export, between the CREATE TABLE and the lines of the extended
inserts.
I did not check this myself.
What about asking the user with an option, the eol style he wants?
The inconsitency is fixed in cvs. Only problem remains that we use Mac eol,
which MySQL won't accept :-)
I'd prefer to make it without options, we have too much of them :-(
--
Michal Čihař | http://cihar.com
7269
days inactive
7269
days old
4 comments
2 participants
participants (2)
-
Marc Delisle -
Michal Čihař