Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you're talking about is a very unfortunate design pattern called serialization: that is, condensing multiple semantically different pieces of data into a single string. It's a bad idea most of the time, and in virtually all cases it's a better idea to separate your data into multiple fields, or even multiple tables. By using serialized fields, you'll find you:</p> <ul> <li>Have much, MUCH slower queries when querying multiple, serialized subfields</li> <li>Complicated queries for updating multiple parts of the same field</li> <li>Feelings of depression and despair</li> </ul> <p>If I had to deal with a database like that, and I couldn't alter the database structure, I'd probably end up doing a lot of the heavy lifting in program code. Many languages have better (or at least, more intuitive) string handling tools than SQL, and your performance benefits from using a RDBMS are going to be marginal at best when dealing with serialization anyway.</p> <p>But if you absolutely must do this in SQL, you should read through Postgres's string handling, located here: <a href="http://www.postgresql.org/docs/9.1/static/functions-string.html" rel="nofollow">http://www.postgresql.org/docs/9.1/static/functions-string.html</a></p> <p>And you're right, your solution is probably going to involve a regex. Exactly what that regex will look like depends on how many serialized fields it has to parse, and exactly how it's delimited. In your example, it looks like each subfield is delimited by a pair of spaces and a pipe character between them, and if that's the case make sure that you either create rules to let you escape that delimiter as needed, or make sure that the frontend never passes the delimeter to the database.</p> <p>Of course, if you have that kind of control over the frontend app, you could give the serialized data its own fields.</p>
    singulars
    1. This table or related slice is empty.
    1. POGet a string slices in two columns in postgres
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWinfield Trail
    1. USWinfield Trail
    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. COOkay, but my quest is find a way to do that with SQL. @sudowned
      singulars
      1. PO
      1. USIrish Wolf
    2. COThen Postgres' string handling functions are where you should be looking: http://www.postgresql.org/docs/9.1/static/functions-string.html
      singulars
      1. PO
      1. USWinfield Trail
 

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