在远程位置托管 SQL？
我的 OSCommerce 站点包含一个单独编程的功能，我使用 SQL 表来实现该功能。我决定将其表托管在提供免费 SQL 帐户的远程站点上。我想知道这种方法是否有任何缺点。
谢谢 西德
My OSCommerce site includes a separately programmed feature for which I use SQL tables. I've decided to host its tables on a remote site offering free SQL accounts. I'd like to know if there could be any disadvantages to this approach.
Thanks
Syd
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
缺点可能包括运行脚本所需的时间较长，因为它必须通过网络建立连接，并且需要确保安全地建立数据库连接 - 数据库登录密码不会传入清晰的文字和连接接收端的权限设置为仅允许来自该 IP 的连接。当然，您还需要确保免费托管公司为数据库本身提供足够的安全性——“免费”并不总是为最好的设置或最有知识的技术人员付费......
Disadvantages might include the longer time it will take to run the script since it has to make a connection over the network and the need to make sure that the database connection is made securely -- that the password for the database login isn't passed in clear text & that the permissions on the receiving end of the connection are set to allow connections from only that IP. Of course you'll also want to make sure that the free hosting company provides adequate security for the database itself -- "free" doesn't alway pay for the best set up or the most knowledgeable technicians...
您应该使用 MySQL 的内置 SSL 功能连接到 MySQL 数据库。这确保了所有传输的数据都受到高度保护。您应该创建自签名 x509 证书并对它们进行硬编码。这是免费的，您不需要像 Verisign 这样的 CA。如果存在证书异常，则存在 MITM，从而阻止您泄露密码。
另一种选择是 VPN，如果您有多个需要安全点对点连接的守护程序，则此选项更适合。
You should connect to your MySQL database using MySQL's built-in SSL ability. This insures that all data transfered is highly protected. You should create self-signed x509 certificates and hard code them. This is free, and you don't need a CA like Verisign for this. If there is a certificate exception then there is a MITM and thus this stops you from spilling the password.
Another option is a VPN, and this is better suited if you have multiple daemons that require secure point to point connections.
我假设您将 OSCommerce 数据库托管在与 Web 服务器相同的服务器上，并且您的解决方案仅为每个客户分配一个数据库。您可以在与常规 OSCommerce 表相同的数据库中使用附加表，只要您为它们添加一些前缀，这样它们就不会出现命名空间冲突。如果第三方解决方案的代码很好，那么配置表前缀就不会太难，以便代码知道表的新名称是什么。这解决了任何潜在的延迟问题并将控制权掌握在您手中。我使用这个技巧在同一个数据库中托管多个 WordPress 博客。
I am assuming you are hosting the OSCommerce database on the same server as the webserver and your solution only allocates one database per customer. You can use the add-on tables in the same database as the regular OSCommerce tables as long as you prefix them with some prefix so that they won't have a namespace conflicts. If the code to the third party solution is any good, it won't be too hard to configure a table prefix so that the code will know what the new names for the tables are. This solves any potential latency problem and keeps the control in your hands. I use this trick to host multiple wordpress blogs in the same database.