首页 \ 问答 \ Sinatra Synchrony与Redis连接池(Sinatra Synchrony with Redis connection pooling)

Sinatra Synchrony与Redis连接池(Sinatra Synchrony with Redis connection pooling)

 这是处理与Sinatra Synchrony的 Redis连接池的正确方法吗？  
 我的gemfile看起来像这样：  
gem 'sinatra-synchrony'
gem 'hiredis'
gem 'redis'
 
 sinatra服务器文件使用经典样式方法，通常如下所示：  
require 'sinatra'
require 'sinatra/synchrony'
require 'redis/connection/hiredis'
require 'redis/connection/synchrony'
require 'redis'

redis = EventMachine::Synchrony::ConnectionPool.new(size: 5) do
  Redis.new(path: '/tmp/redis.sock')
end

get / do
  # lots of redis reads and writes
end
 
 然后，我启动同一服务器应用程序的多个实例，每个实例位于不同的端口下，并使用nginx在它们之间进行负载平衡。  
 这是Redis与Sinatra服务器连接池的正确解决方案吗？ 

Is this the correct way of handling Redis connection pooling with Sinatra Synchrony? 
My gemfile looks like this: 
gem 'sinatra-synchrony'
gem 'hiredis'
gem 'redis'
 
The sinatra server files use the classic style approach, and generally look like so: 
require 'sinatra'
require 'sinatra/synchrony'
require 'redis/connection/hiredis'
require 'redis/connection/synchrony'
require 'redis'

redis = EventMachine::Synchrony::ConnectionPool.new(size: 5) do
  Redis.new(path: '/tmp/redis.sock')
end

get / do
  # lots of redis reads and writes
end
 
I then launch multiple instances of the same server application, each under a different port, and use nginx to load balance between them. 
Is this the proper solution for connection pooling Redis with Sinatra servers?

原文：https://stackoverflow.com/questions/8856001

更新时间：2022-10-30 12:10

最满意答案

 语法明智这是不正确的。  
 问题在这里得到解决：  
CREATE TABLE Venue (
     venueID VARCHAR(20), 
     venueEmail VARCHAR(30) NOT NULL, 
     address VARCHAR(100), 
     phoneNo VARCHAR(20), 
     managerNo VARCHAR(20), 
     capacity INT(4), 
     PRIMARY KEY (venueEmail)
)ENGINE=InnoDB;

CREATE TABLE Concert (
     referenceNo VARCaHAR(6), 
     venueEmail VARCHAR(30), 
     eventDate VARCHAR(10),
     startTime VARCHAR(5),
     ticketsSold INT(4),
     PRIMARY KEY (referenceNo), 
     FOREIGN KEY (venueEmail) REFERENCES Venue(`venueEmail`) ON UPDATE CASCADE ON DELETE CASCADE
)ENGINE=InnoDB;
 
 
 注意：  
 引用的列应该类似于table_name(column_name) 。  
 你错过了column_name部分。  
 
 参考  
 
 更多：  
 @Bill Karwin在评论部分添加了以下有用信息：  
 
  FWIW这是一个MySQL的特质。 在标准SQL中，如果省略引用的列名，则默认使用与外键列相同的名称。 但InnoDB不支持此快捷方式语法 - 您必须在两种情况下都指定列。  

Syntax wise this isn't correct. 
The issue's resolved here: 
CREATE TABLE Venue (
     venueID VARCHAR(20), 
     venueEmail VARCHAR(30) NOT NULL, 
     address VARCHAR(100), 
     phoneNo VARCHAR(20), 
     managerNo VARCHAR(20), 
     capacity INT(4), 
     PRIMARY KEY (venueEmail)
)ENGINE=InnoDB;

CREATE TABLE Concert (
     referenceNo VARCaHAR(6), 
     venueEmail VARCHAR(30), 
     eventDate VARCHAR(10),
     startTime VARCHAR(5),
     ticketsSold INT(4),
     PRIMARY KEY (referenceNo), 
     FOREIGN KEY (venueEmail) REFERENCES Venue(`venueEmail`) ON UPDATE CASCADE ON DELETE CASCADE
)ENGINE=InnoDB;
 
 
Note:  
The column being referenced should be stated like table_name(column_name). 
You missed the column_name part. 
 
REFERENCE 
 
More: 
@Bill Karwin added the following useful info in the comment section: 
 
 FWIW this is a MySQL idiosyncrasy. In standard SQL, if you omit the referenced column name, it defaults to the same name as the foreign key column. But InnoDB doesn't support this shortcut syntax—you must specify the column in both cases.

Sinatra Synchrony与Redis连接池(Sinatra Synchrony with Redis connection pooling)

最满意答案

相关问答

MySQL错误1215：无法添加外键约束(MySQL Error 1215: Cannot add foreign key constraint)[2022-11-16]

错误1215 MySQL无法添加外键约束(Error 1215 MySQL Cannot add foreign key constraint)[2022-10-25]

1215无法添加外键约束(1215 Cannot add foreign key constraint)[2024-02-03]

“1215 - 不能添加外键约束”(“1215 - cannot add foreign key constraint”)[2023-10-11]

MySQL - 错误1215 - 无法添加外键约束(MySQL - Error 1215 - Cannot add foreign key constraint)[2023-04-27]

一般错误1215：无法添加外键约束(General error 1215: cannot add foreign key constraint)[2024-01-17]

MySQL错误1215 - 无法添加外键约束(MySQL Error 1215 - Cannot add foreign key constraint)[2022-09-23]

MYSQL错误：错误1215：无法添加外键约束(MYSQL ERROR: Error 1215: Cannot add foreign key constraint)[2022-11-30]

MySQL - 错误1215，无法添加外键约束(MySQL - error 1215, cannot add foreign key constraint)[2023-07-21]

MySql错误1215：无法添加外键约束(MySql error 1215: Cannot add foreign key constraint)[2022-04-12]

相关文章

最新问答