Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you probably want something like</p> <pre><code>def get_diagonal(t, x, y, length=4): rays = [] diagonal_directions = [(1,1),(1,-1),(-1,1),(-1,-1)] for dx, dy in diagonal_directions: if not ((0 &lt;= (x+dx*(length-1)) &lt; len(t[0])) and (0 &lt;= (y+dy*(length-1)) &lt; len(t))): ray = [] else: ray = [t[y+dy*i][x+dx*i] for i in range(length)] rays.append(ray) return rays </code></pre> <p>[Better: remove <code>rays</code> entirely and simply <code>yield</code> each ray.]</p> <p>I always mix up <code>x</code> and <code>y</code> when doing this stuff, so you'll want to check that, but I think something like this should work. Example:</p> <pre><code>In [48]: get_diagonal(t, 0, 0) Out[48]: [[8, 49, 31, 23], [], [], []] In [49]: get_diagonal(t, 19, 19) Out[49]: [[], [], [], [48, 5, 4, 40]] In [50]: get_diagonal(t, 5, 5) Out[50]: [[3, 67, 20, 97], [3, 63, 42, 93], [3, 64, 68, 58], [3, 51, 23, 31]] In [51]: get_diagonal(t, 5, 5, 3) Out[51]: [[3, 67, 20], [3, 63, 42], [3, 64, 68], [3, 51, 23]] </code></pre> <p>You can change the order of <code>diagonal_directions</code> to match your expectations. Also, note that I'm returning <code>[]</code> instead of <code>[0,0,0,0]</code> if you don't have enough terms. Returning <code>[0,0,0,0]</code> is a bad idea, ISTM -- how would you distinguish between not having enough terms and having the right number of terms but they're all zero? It feels weird to me to load that logic into the diagonal function, but you could easily change that.</p>
    singulars
    1. This table or related slice is empty.
    1. POfinding diagonal numbers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDSM
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POfinding diagonal numbers
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAwesome man! I think I was on the right track but not quite there.
      singulars
      1. PO
      1. USFabianCook
    2. CONow for the rest of the problem. xD. Wouldn't happen to have any code to do up, down, left and right would you? In the same format...
      singulars
      1. PO
      1. USFabianCook
    3. CO@SmartLemon: I'll leave that to you. If you understand what `dx` and `dy` mean, you should be able to figure out how you can use the same approach to get those directions to work -- or how to get a knight's step to work, for that matter.
      singulars
      1. PO
      1. USDSM
 

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