Databases
StackOverflow2013
Postsdbo
POSELECT * INTO OUTFILE from a view doesn't work, but the underlying query works fine INTO OUTFILE
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSELECT * INTO OUTFILE from a view doesn't work, but the underlying query works fine INTO OUTFILE
    primarykey
    data
    text
    <p>I'm running a query that does a calculation based on some views, and writes the results to a file. It looks like this:</p> <pre><code>select `v1`.`id` AS `id`,`v2`.`name` AS `name`, `v2`.`nbr` AS `nbr`, `v1`.`nbr` AS `total`, (`v2`.`nbr` / `v1`.`nbr`) AS `percent` INTO OUTFILE '/home/username/mysqldump/filename.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n' from `v2` join `v1` where `v2`.`id` = `v1`.`id` </code></pre> <p>That works great. I created a view based on this query, but it doesn't work as a drop-in replacement, as I expected. Here's the "Create View" portion of SHOW CREATE VIEW: </p> <pre><code> CREATE ALGORITHM=UNDEFINED DEFINER=`user`@`localhost` SQL SECURITY DEFINER VIEW `view_name` AS select `v1`.`id` AS `id`, `v2`.`name` AS `name`, `v2`.`nbr` AS `nbr`, `v1`.`nbr` AS `total_pvs`, (`v2`.`nbr` / `v1`.`nbr`) AS `percent` from (`v2` join `v1`) where (`v2`.`id` = `v1`.`id`) </code></pre> <p>Here's the query that doesn't work:</p> <pre><code> SELECT * INTO OUTFILE '/home/username/mysqldump/filename.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n' FROM view_name; </code></pre> <p>I got this error:</p> <p><code>ERROR 1356 (HY000): View 'database_name.view_name' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them</code></p> <p>I'm running as root, so I don't think there are any rights issues. What might be making this query invalid in the eyes of MySQL? I'm running version 5.5.32-0ubuntu0.12.04.1 (Ubuntu)</p> <p><strong>EDIT</strong>: Running <code>SELECT * FROM view_name</code> returns the records as expected. However, with thousands of lines, and the need for solid formatting, I would rather use <code>INTO OUTFILE</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMartin Burch
    1. USMartin Burch
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COPlease show the definition of the view. You also removed the `FIELDS TERMINATED`, etc., right?
      singulars
      1. POSELECT * INTO OUTFILE from a view doesn't work, but the underlying query works fine INTO OUTFILE
      1. USwallyk
    2. COI did indeed, yes. I added the create view statement so you won't have to just take my word for it. Do you see something odd in there?
      singulars
      1. POSELECT * INTO OUTFILE from a view doesn't work, but the underlying query works fine INTO OUTFILE
      1. USMartin Burch
    3. COIt looks fine. All I can think of is that the view is not correctly defined by referencing some fields that do not exist.
      singulars
      1. POSELECT * INTO OUTFILE from a view doesn't work, but the underlying query works fine INTO OUTFILE
      1. USwallyk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload