artisonian

eventsource
go-eventsource
client/client

everdaniel

-- Function: im_detalle_1_actualiza_ingreso()

-- DROP FUNCTION im_detalle_1_actualiza_ingreso();

CREATE OR REPLACE FUNCTION im_detalle_1_actualiza_ingreso()
  RETURNS trigger AS
$BODY$
DECLARE
  -- Declaramos las variables con el mismo tipo del definido en la tabla
  iva_5 ingreso_mercaderia.im_impuesto_5%TYPE;

lttlrck

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

ismasan

// Copyright (c) 2017 Ismael Celis

// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:

// The above copyright notice and this permission notice shall be included in all

ryboe

OBSOLETE PREFIXES
    -xv-interpret-as      // -xv- and -o- are old Opera prefixes for the Presto
    -xv-phonemes          // engine. Opera switched to the Blink engine with
    -xv-voice-balance     // version 15. The current version is 34.
    -xv-voice-duration
    -xv-voice-pitch
    -xv-voice-pitch-range
    -xv-voice-rate
    -xv-voice-stress
    -xv-voice-volume

abdullin

This is my response to an email asking about Domain-Driven Design in golang project.

Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.

That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.

Conclusions could be very different, if there was a different project, team or a story-teller.

Short story

obolton

AWS ELB with Node.js and WebSockets

This assumes that:

• You are using Nginx.
• You want to accept incoming connections on port 80.
• Your Node.js app is listening on port 3000.
• You want to be able to connect to your Node.js instance directly as well as via the load balancer.

####1. Create load balancer

alexedwards

.
├── books
│   ├── handlers.go
│   └── models.go
├── config
│   └── db.go
└── main.go

tommypeps

@"[ A-Za-zäÄëËïÏöÖüÜáéíóúáéíóúÁÉÍÓÚÂÊÎÔÛâêîôûàèìòùÀÈÌÒÙ.-]+"

gokulkrishh

/* 
  ##Device = Desktops
  ##Screen = 1281px to higher resolution desktops
*/

@media (min-width: 1281px) {
  
  /* CSS */