zcaceres

'Include' in Sequelize: The One Confusing Query That You Should Memorize

When querying your database in Sequelize, you'll often want data associated with a particular model which isn't in the model's table directly. This data is usually typically associated through join tables (e.g. a 'hasMany' or 'belongsToMany' association), or a foreign key (e.g. a 'hasOne' or 'belongsTo' association).

When you query, you'll receive just the rows you've looked for. With eager loading, you'll also get any associated data. For some reason, I can never remember the proper way to do eager loading when writing my Sequelize queries. I've seen others struggle with the same thing.

Eager loading is confusing because the 'include' that is uses has unfamiliar fields is set in an array rather than just an object.

So let's go through the one query that's worth memorizing to handle your eager loading.

The Basic Query

ravibhure

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

tzmartin

Module not found: Error: Cannot resolve module 'remote'

The fix:

• Install webpack-target-electron-renderer module, or
• Use Webpack externals definitions:

protrolium

ffmpeg

Converting Audio into Different Formats / Sample Rates

Minimal example: transcode from MP3 to WMA:
ffmpeg -i input.mp3 output.wma

You can get the list of supported formats with:
ffmpeg -formats

You can get the list of installed codecs with:

ideaoforder

openssl req -new -newkey rsa:2048 -nodes -keyout yourdomain.key -out yourdomain.csr

http://support.godaddy.com/help/article/3601/generating-a-certificate-signing-request-nginx
http://support.godaddy.com/help/article/4976/rekeying-an-ssl-certificate

# Be sure to remember to chain them!
cat gd_bundle-g2-g1.crt >> yourdomain.crt

# Move 'em
sudo mv yourdomain.crt /etc/ssl/certs/yourdomain.crt

phoenixlzx

301 https://github.com/zxdrive/imouto.host

ambar

// ==UserScript==
// @name          nospm
// @version       1.4.0
// @run-at        document-start
// @updateURL     https://gist.github.com/ambar/9706385/raw/nospm.user.js
// @downloadURL   https://gist.github.com/ambar/9706385/raw/nospm.user.js
// @description   移除 Bilibili、淘宝、天猫、优酷网址中的 spm 参数（包括地址栏和页面中的链接）
// @include       https://*.bilibili.com/*
// @include       https://*.taobao.com/*
// @include       https://*.tmall.com/*

thoop

# Change YOUR_TOKEN to your prerender token
# Change example.com (server_name) to your website url
# Change /path/to/your/root to the correct value

server {
    listen 80;
    server_name example.com;
 
    root   /path/to/your/root;
    index  index.html;

plentz

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

tedmiston

/*
In the node.js intro tutorial (http://nodejs.org/), they show a basic tcp 
server, but for some reason omit a client connecting to it.  I added an 
example at the bottom.

Save the following server in example.js:
*/

var net = require('net');