如何在Python中使用切片来选择其他的(How to select every other using slicing in Python)

 对您的成品进行负载测试并证明访问不适用于为网站提供动力。 
 
 编写代码，以便您可以轻松更换数据库后端。 然后，当访问失败时，将数据迁移到真正的数据库，或者MySQL，如果必须的话。 
 
 以下是一些Microsoft Web服务器压力工具 
 
 为了记录，可以将大多数SQL命令发送到数据库，而不是保持活动连接处于打开状态，从而一次允许远远超过6或7个连接，但事实是访问并不意味着这样做。 因此，“它工作正常”的意思就好像说用胶带清理地板很好：它可以工作，但不适合工作。 
 
 更新问题的更新答案： 
 
 真的，这里的关键是在代码中分离数据访问。 您应该能够在任何数量的DBMS中或多或少地拥有数据库结构。 事情可能会变得复杂，但是表格图应该是通用的。 然后应该访问不起作用，决定使用不同的数据库。 
 
 访问可用于高流量的网站。 通过仅使用SQL语句的例程，我能够建立一个电子商务网站，每年销售额达到几百万，并且每个月有60,000个访问者。 这是可能的，但可能并不理想。 这些数字并不是很大，但对于我参与过的任何网站来说，它们是最大的。 
 
 如果IT经理太忙而无法维护另一台服务器，或者不愿花时间配置其他服务器，请保持访问权限。 最终猜测什么都不做，并且测试告诉你你需要知道的一切。 测试并对结果做出决定。 

Do a load test on your finished product and prove that Access isn't meant for powering websites.
 
Write your code so that you can change out the database back end easily. Then when access fails migrate your data to a real db, or MySQL if you have to.
 
Here are some Microsoft Web server stress tools
 
For the record, it is possible to send mostly SQL commands to the database and not keep an active connection open, thereby allowing far more than 6 or 7 connections at once, but the fact is that access just isn't meant to do it. So the "it works fine" point is like saying it is fine to clean your floor with sticky tape: it works, but isn't the right tool for the job.
 
UPDATED ANSWER TO UPDATED QUESTION:
 
Really the key here is the separation of data access in your code. You should be able to more or less have the data database structure in any number of DBMS. Things can get complicated, but a map of tables should be universal. Then should access not work, decide to use a different database.
 
Access CAN be used in kinda high traffic sites. With the SQL statement only routines I was able to build an e-commerce site that did a couple million a year in sales, and had 60K visitors a month. It is possible, but maybe not ideal. Those aren't big numbers, but they are the biggest for any site I have been a part of.
 
Keep access if IT Manager is too busy to maintain another server, or unwilling to spend time configuring one. Ultimately guessing does nothing, and testing tells you everything you need to know. Test and make decisions on the results.