Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Ok think I got something here. That's a weird one... Actually it does not work if you have the same schema exactly (field mode).</p> <p>Here is the source table schema:</p> <pre><code> "schema": { "fields": [ { "name": "ID_CLIENT", "type": "INTEGER", "mode": "NULLABLE" }, { "name": "IDENTITE", "type": "STRING", "mode": "NULLABLE" } ] } </code></pre> <p>If if I use the copy functionality from the browser interface (bigquery.cloud.google.com), I get the exact same schema which is expected:</p> <pre><code>"schema": { "fields": [ { "name": "ID_CLIENT", "type": "INTEGER", "mode": "NULLABLE" }, { "name": "IDENTITE", "type": "STRING", "mode": "NULLABLE" } ] } </code></pre> <p>But then I cannot append from the following fetch to the copied table:</p> <pre><code>SELECT ID_CLIENT + 1 AS ID_CLIENT, RIGHT(IDENTITE,12) AS IDENTITE FROM datasetid.client </code></pre> <p>although it returns the same schema, at least from the browser interface view, internally this returns the following schema:</p> <pre><code>"schema": { "fields": [ { "name": "ID_CLIENT", "type": "INTEGER", "mode": "REQUIRED" }, { "name": "IDENTITE", "type": "STRING", "mode": "NULLABLE" } ] </code></pre> <p>}</p> <p>Which isn't the same schema exactly (check mode).</p> <p>And weirder this select:</p> <pre><code>SELECT ID_CLIENT, IDENTITE FROM datasetid.client </code></pre> <p>returns this schema:</p> <pre><code>"schema": { "fields": [ { "name": "ID_CLIENT", "type": "INTEGER", "mode": "REQUIRED" }, { "name": "IDENTITE", "type": "STRING", "mode": "REQUIRED" } ] } </code></pre> <p>Conclusion:</p> <p>Don't rely on tables schema information from the browser interface, always use Tables.get API. Copy doesn't really work as expected...</p>
    singulars
    1. This table or related slice is empty.
    1. POAppend data from SELECT to existing table
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCharles
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMy question is how can you append data from a SELECT since you cannot force the fetched result schema's fields mode?
      singulars
      1. PO
      1. USCharles
    2. CO1. How was the original table created? Via a load / import operation? 2. What is it about table copy that doesn't work as expected? 3. If you have a brand new table, and run two identical queries with write_append, does that work?
      singulars
      1. PO
      1. USJordan Tigani
    3. CO1. The original table was created with the bq commandline tool mk -t command then bq load operation 2. Sorry I didn't mean table copy (my bad) but more the Jobs.insert API functionality with the writeDisposition option set to 'WRITE_APPEND' 3. If you mean to create a brand new table from a SELECT and then run this SELECT again, yes this appends properly. The problem is that you have to always run the same query since the schema that is deduced from your fetch seems unpredictable.
      singulars
      1. PO
      1. USCharles
 

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