fritzy

function promiser(input) {
  if (input === 1) {
    return Promise.resolve(input);
  }
  if (input === 2) {
    return Promise.reject(new Error('Rejected'));
  }
  throw new Error('Broken');
}

fritzy

CREATE EXTENSION IF NOT EXISTS "pgcrypto";

-- Create a trigger function that takes no arguments.
-- Trigger functions automatically have OLD, NEW records
-- and TG_TABLE_NAME as well as others.
CREATE OR REPLACE FUNCTION unique_short_id()
RETURNS TRIGGER AS $$

 -- Declare the variables we'll be using.
DECLARE

fritzy

Pros:

• Shallow Learning Curve
• Easy to get and app running

Cons:

• It's not composable.
• DDP is not used anywhere else, REST is, and you'd have to do that in addition to your app.
• Only MongoDB support right now, which we consider a marketing driven product with a troubled history rather than a technical driven tool (although Postgres support is in the works)
• Making React views in Meteor client-side is not the point -- the front-end is tightly coupled to the backed via DDP, having the server direct the client state and causing many edge cases.
• The biggest use case for Meteor is a niche edge case -- simultaneously editing the same field, and can be solved via standards and small packages.

fritzy

const someObject = {};

const someProxy = new Proxy(someObject, {
  get: function (target, property, reciever) {
    if (property.substr(0, 6) === 'happy_') {
      return Reflect.get(target, property.substr(6), reciever);
    }
    return 'sad';
  },
  set: function (target, property, value, reciever) {

fritzy

module.exports = function (server, options, next) {
  console.log('loading plugin');

  server.ext({
    type:'onPostAuth',
    method: function (request, reply) {

      var req = request.raw.req;
      var res2 = reply.response
      var headers = {};

fritzy

SELECT json_build_object(
  'total', (SELECT n_live_tup FROM pg_stat_user_tables WHERE relname='sometable'),
  'count', count(sometable_rows.*),
  'offset', 0,
  'results', json_agg(row_to_json(sometable_rows))
)
FROM (SELECT * FROM sometable
ORDER BY "time"
LIMIT 10 OFFSET 0)
sometable_rows;

fritzy

//POTENTIALLY DANGEROUS

pg.query('SET ROLE fritzy', function (err) {
  //this doesn't happen until the event loop calls it after SET ROLE
  //you don't know if the role has been changed since then on this connection
  //your next query could be ANY role
  pg.query('INSERT INTO some_table (...) VALUES (...)', function (err, result) {
    // ...
  });
});

fritzy

CREATE OR REPLACE FUNCTION generate_update_query(value JSON, tbl TEXT) RETURNS TEXT as $$
DECLARE
    key TEXT;
    sets TEXT[];
BEGIN
    FOR key IN
        SELECT json_object_keys(value)
    LOOP
        IF (key != 'id') THEN
            SELECT array_append(sets, format('%I=%L', key, value->>key)) INTO sets;

fritzy

CREATE OR REPLACE FUNCTION table_update_notify() RETURNS trigger AS $$
DECLARE
  id bigint;
BEGIN
  IF TG_OP = 'INSERT' OR TG_OP = 'UPDATE' THEN
    id = NEW.id;
  ELSE
    id = OLD.id;
  END IF;
  PERFORM pg_notify('table_update', json_build_object('table', TG_TABLE_NAME, 'id', id, 'type', TG_OP)::text);

fritzy

fritzy=# select * from authors2;
 id |     name
----+--------------
  1 | Nathan Fritz
(1 row)

fritzy=# select * from books2;
 id |         title         | author_id
----+-----------------------+-----------
  1 | Happy Fun Times       |         1