Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The big problem here isn't really what your library does with the values (which is a potential problem, albeit a much more manageable one), but rather what callers might do with the values. If you need to treat them as immutable, then you need to ensure that a library consumer cannot change the contents after their original assignment. The easy fix here would be to create an interface that exposes all the array members that your library uses, then create an immutable wrapper class for an array that implements this interface to use in your <code>InputObject</code> class. <em>e.g.</em>:</p> <pre><code>public interface IArray&lt;T&gt; { int Length { get; } T this[int index] { get; } } internal sealed class ImmutableArray&lt;T&gt; : IArray&lt;T&gt; where T : struct { private readonly T[] _wrappedArray; internal ImmutableArray(IEnumerable&lt;T&gt; data) { this._wrappedArray = data.ToArray(); } public int Length { get { return this._wrappedArray.Length; } } public T this[int index] { get { return this._wrappedArray[index]; } } } public class InputObject { private readonly IArray&lt;double&gt; _x; private readonly IArray&lt;double&gt; _y; public InputObject(double[] x, double[] y) { this._x = new ImmutableArray&lt;double&gt;(x); this._y = new ImmutableArray&lt;double&gt;(y); } public IArray&lt;double&gt; X { get { return this._x; } } public IArray&lt;double&gt; Y { get { return this._y; } } //... } </code></pre> <p>The elements in your "immutable" array contents would still be mutable if T is mutable, but at least you're safe for the double type.</p>
    singulars
    1. This table or related slice is empty.
    1. POCA1819: Properties shouldn't return arrays - What is the right alternative?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USNicole Calinoiu
    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. This table or related slice is empty.
    1. COSeems overkill to create your own interface (IArray) rather than using the similar IList<T> that already exists in the framework.
      singulars
      1. PO
      1. USJoe
    2. CO@Joe: IList<T> exposes operations for modifying the list. Items can be added, removed, and swapped out. Of course, one could throw a NotSupportedException for each of the mutation points, but that's not a particularly polite way to treat API consumers. And seriously, how much trouble is it to add an interface?
      singulars
      1. PO
      1. USNicole Calinoiu
    3. COit also a property IsReadOnly, which allows a caller to avoid the NotSupportedException. The idiomatic way to handle this in .NET is to expose a readonly IList<T>, probably backed by a ReadOnlyCollection<T>. Your current implementation has a number of weaknesses, including failing to implement IEnumerable<T>, ICollection<T> and IList<T>, which would be expected of an array class. You could spend time implementing these, but why would you do so when the Framework already contains all you need?
      singulars
      1. PO
      1. USJoe
 

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