2009/8/18 Terrence Brannon :
> Hello, when converting a .sql file containing MySQL INSERT clauses,
> one often runs into the problem that the MySQL INSERT can accept
> multiple VALUES arguments:
>
>INSERT INTO actor VALUES (1,'PENELOPE','GUINESS','2006-02-15
>
On Tue, Aug 18, 2009 at 09:42:53AM -0500, Beau Wilkinson scratched on the wall:
> >On Tue, Aug 18, 2009 at 08:28:13AM -0500, Beau Wilkinson scratched on the
> >wall:
> > It is also worth noting that every non-SQL Relational language (e.g.
> > Tutorial-D) I've looked at supports some form of
On 18/08/2009 11:28 PM, Beau Wilkinson wrote:
> That said, if you're in posession of the source code,
> you can certainly hack something up to support that.
> A better option might be to pre-process the MySQL file
> using C, Perl, XSLT (just kidding - don't use XSLT)
> or whatever else you
>On Tue, Aug 18, 2009 at 08:28:13AM -0500, Beau Wilkinson scratched on the wall:
>> To me that seems like an annoying deviation from standard practice.
>> Do other databases support such an INSERT?
>
>Yes. MySQL, PostgreSQL, and SQLServer all support this syntax.
>
>Oracle supports a slightly
On Tue, Aug 18, 2009 at 08:28:13AM -0500, Beau Wilkinson scratched on the wall:
> To me that seems like an annoying deviation from standard practice.
> Do other databases support such an INSERT?
Yes. MySQL, PostgreSQL, and SQLServer all support this syntax.
Oracle supports a slightly
To me that seems like an annoying deviation from standard practice. Do other
databases support such an INSERT? Is it envisioned by standards? I suspect the
answer is "no" in both cases, and this is a classic example of how "less"
functionality is actually "more" useful.
That said, if you're in
6 matches
Mail list logo