Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First off - I think you have the technical basis to develop an excellent serializer. That said, I find various aspects of the ProtoBuf serialization so impractical that I cannot see myself using it in its current status.</p> <p>Let me qualify - First off, with the explicit need for having the ProtoBuf attributes on a class for it to serialize forces a ProtoBuf deployment dependency; while one of the basic ideas behind serialization is that one could take the same classes, and swopping out serializer(s) if/when needed - meaning that the attributes and dll may be not be needed for different deployments.</p> <p>2nd off - with ProtoBuf not by default recursing the inheritance tree makes it even more Protobuf specific - meaning more clutter in the code, more specific code dependency etc. This is a very obvious flaw in my opinion, as if one derives B from A, then one would naturally want the properties of A to be included when serializing B - without the custom code as shown in the thread above.</p> <p>Thirdly - picture yourself that there is no need for the attributes... then you can also picture yourself serializing from objects e.g. object[] Parameters - which ProtoBuf cannot currently do. I guess (not being a serialization expert myself), that it may be as simple as putting the class and assembly as part of the the serialized object to resolve it remotely - keeping in mind that the same library must reside there as well. In other words, the ability to serialize any type / type hierarchy, without explicit attributes, based on the assumption that the same types by name and assembly will exist on the remote machine.</p> <p>Marc, good luck with your implementation.</p> <p>Gawie</p>
    singulars
    1. This table or related slice is empty.
    1. POProtobuf-net include specific member of non-serializable base class
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USuser1210708
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI guess I am looking at it the wrong way... in retrospect it is probably more of an inter-language communication tool rather than a .NET feature rich serialization sdk...
      singulars
      1. PO
      1. USuser1210708
 

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