Hi, In 3.5.x I suggest replacing @FIELDS@ with @COLUMNS@ to comply with standard SQL terminology.
See http://www.phpmyadmin.net/documentation/#faq6_27.
Hi
Dne Sat, 01 Oct 2011 07:13:20 -0400 Marc Delisle marc@infomarc.info napsal(a):
Hi, In 3.5.x I suggest replacing @FIELDS@ with @COLUMNS@ to comply with standard SQL terminology.
Okay for me, probably we could keep the latter one for backward compatibility (or remove dozen of other backward compatibility replacements).
2011/10/3 Michal Čihař michal@cihar.com:
Hi
Dne Sat, 01 Oct 2011 07:13:20 -0400 Marc Delisle marc@infomarc.info napsal(a):
Hi, In 3.5.x I suggest replacing @FIELDS@ with @COLUMNS@ to comply with standard SQL terminology.
Okay for me, probably we could keep the latter one for backward compatibility (or remove dozen of other backward compatibility replacements).
Fine for me.
Kind regards,
Dieter
Michal Čihař a écrit :
Hi
Dne Sat, 01 Oct 2011 07:13:20 -0400 Marc Delisle marc@infomarc.info napsal(a):
Hi, In 3.5.x I suggest replacing @FIELDS@ with @COLUMNS@ to comply with standard SQL terminology.
Okay for me, probably we could keep the latter one for backward compatibility (or remove dozen of other backward compatibility replacements).
Yes, we can keep @FIELDS@ in the code but remove it from the doc (for 3.5).
Hi
Dne Mon, 03 Oct 2011 10:01:30 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Sat, 01 Oct 2011 07:13:20 -0400 Marc Delisle marc@infomarc.info napsal(a):
Hi, In 3.5.x I suggest replacing @FIELDS@ with @COLUMNS@ to comply with standard SQL terminology.
Okay for me, probably we could keep the latter one for backward compatibility (or remove dozen of other backward compatibility replacements).
Yes, we can keep @FIELDS@ in the code but remove it from the doc (for 3.5).
That's exactly what I meant.