blocks|key|91918|text|那么，顺序应该独立于表。实际上，您应该有一个由seat/+customer对象组成的表对象和一个由一个或多个项目组成的订单对象(其中项目具有名称、数量、价格或属于某个项目的任何其他内容)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91919|作为一个额外的复杂性，一个订单既可以属于一个座位(一个人)，也可以属于一个桌子(例如，共享开胃菜)。支持这种关系将允许您在尝试为表编译账单时做不同的事情(例如，如果您必须提供拆分检查)。|91920|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, orders should be independent of tables. Really you'd have a table object that consisted of seat/ customer objects and an order object that consisted of one or more items (with items having name, quantity, price or whatever else belongs to an item).

As an additional complication, an order could either belong to a seat (one person) or a table (e.g., shared appetizer). Supporting that relationship would allow you to do different things when trying to compile the bill for the table (like if you had to provide split checks).

blocks|key|91947|text|您不需要number_of_items，因为您可以从item数组中获得它，因此您将需要一个items数组。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91948|var+order+=+{
++++id:+0,
++++table:+0,
++++items:+[]
};|code-block|syntax|javascript|91949|理想情况下，您可能希望为item创建另一个类，并将它们的列表放入items数组中。|91950|它看起来是这样的：|91951|items+=+[{name:+"",+quantity:+0,+unit_price:+0},+{...},+{...}]|91952|您可以通过循环遍历数组并进行数学运算来获得总数。|91953|除非数学过于复杂，否则我倾向于不将可导出值存储在对象中，但这正是我所做的。|91954|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

You don't need the number_of_items as you can get that from the item array, so you will want to have an array of items.

<pre><code>var order = {
 id: 0,
 table: 0,
 items: []
};
</code></pre>

Ideally you may want to have another class for item and just put a list of them in your items array.

It would look like:

<pre><code>items = [{name: "", quantity: 0, unit_price: 0}, {...}, {...}]
</code></pre>

You can get the total by looping through the array and do the math.

Unless the math is overly complex I tend to prefer to not have derivable values stored in the object, but that is just what I do.

blocks|key|311994|text|这个怎么样？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|311995|+order+=+{
+++++id:+<unique+identifier>,
+++++table:+<table+number>,
+++++items+:+<array+of+objects+as+declared+below>+
+}

+item+=+{
++++item_id:+<id+of+the+item+in+the+menu>
++++instructions+:+<text>
+}|code-block|syntax|javascript|311996|备注：|311997|311998|number+of+items+=项目数组的长度。|unordered-list-item|311999|单价属于菜单对象。|312000|总数可以随时计算。|312001|不要忘记说明(烹饪，上菜)！|312002|312003|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|11|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

How about this?

<pre><code> order = {
 id: &lt;unique identifier&gt;,
 table: &lt;table number&gt;,
 items : &lt;array of objects as declared below&gt; 
 }

 item = {
 item_id: &lt;id of the item in the menu&gt;
 instructions : &lt;text&gt;
 }
</code></pre>

Notes: 

<ul>
<li>number of items = length of items array. </li>
<li>unit price belongs to menu object. </li>
<li>total can be calculated any time.</li>
<li>Don't forget the instructions (cooking, serving)!</li>
</ul>

blocks|key|1613485|text|有多个表，每个表可以-over一个服务的过程-有几个订单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1613486|我认为您的系统的基本组件/对象应该是封面本身，由以下内容组成：|1613487|order_id、餐桌、菜(至少一道菜)、所选菜肴及其费用、点菜的时间(这看起来可能不重要，但通常是对好的酒店或服务经理而言)和饮料。|1613488|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

There are multiple tables, and each table can -over the course of a service- have several orders.

I would think the basic component/object of your system would be the cover itself, consisting of something along the lines of:

order_id, the table, the course (there'll be a minimum of one course), the chosen dish and its cost, the time of ordering (this may not seem important, but it usually is to a -good- maitre d'hotel or service manager) and the drinks.

blocks|key|1613495|text|我认为你可以在你的结构中去掉一些多余的元素：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1613496|var+order+=+{
++++id:+445221,
++++table:+42,
++++items:+[
++++++++{
++++++++++++name:+"Steak",
++++++++++++quantity:+1,
++++++++++++unit_price:+15
++++++++},
++++++++{
++++++++++++name:+"Beer",
++++++++++++quantity:+1,
++++++++++++unit_price:+3
++++++++}
++++]
};|code-block|syntax|javascript|1613497|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I think you can do away with some redundant elements in your structure:

<pre><code>var order = {
 id: 445221,
 table: 42,
 items: [
 {
 name: "Steak",
 quantity: 1,
 unit_price: 15
 },
 {
 name: "Beer",
 quantity: 1,
 unit_price: 3
 }
 ]
};
</code></pre>

blocks|key|92091|text|除了其他答案之外，特殊的准备说明是什么？您是想要单独的汉堡菜(汉堡--三分熟，汉堡--全熟)，还是想要一张单独的桌子，上面有与该菜相关的烹饪说明？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|92092|你的答案真的取决于你的受众。它是放在厨房的屏幕上，还是让女服务员、收银员、卫生检查员或以上所有人使用？|92093|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In addition to the other answers, what about special preparation directions? Do you want separate Burger items (Burger-medium rare, Burger-well done), or do you want a separate table with the cooking directions linked to that item?

Your answer really depends on your audience. Is it for the screen in the kitchen, for the waitress entering the order, the cashier, the health inspector, or all of the above?

blocks|key|1497182|text|这里有一种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1497183|function+item(name,+price)
{
++++this.name+=+name;
++++this.price+=+price;
}

function+order(id,+table)
{
++++this.id+=+id;
++++this.table+=+table;
++++this.items+=+[];
}

order.prototype.countItems+=+function()
{
++++return+this.items.length;
}

order.prototype.getTotal+=+function()
{
++++var+total+=+0.0;
++++for(var+i+=+0;i+<+this.items.length;+i%2B%2B)
++++{
++++++++total+%2B=+this.items[i].price;
++++}
++++return+total;
}

var+myorder+=+new+order(1234,+12);

myorder.items.push(new+item("coke",+1.25));|code-block|syntax|javascript|1497184|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here is one way.

<pre><code>function item(name, price)
{
 this.name = name;
 this.price = price;
}

function order(id, table)
{
 this.id = id;
 this.table = table;
 this.items = [];
}

order.prototype.countItems = function()
{
 return this.items.length;
}

order.prototype.getTotal = function()
{
 var total = 0.0;
 for(var i = 0;i &lt; this.items.length; i++)
 {
 total += this.items[i].price;
 }
 return total;
}

var myorder = new order(1234, 12);

myorder.items.push(new item("coke", 1.25));
</code></pre>

blocks|key|92128|text|我认为对象的识别需要在任何编码之前进行(抵制编码的冲动)。一些对象包括(一些已经确定)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|92129|92130|table|unordered-list-item|92131|waiter|92132|item+(标准菜单项的预定义列表以及每日特价菜和特殊订单的功能)|92133|+order+(菜单项分组)每张桌子可以有多个订单，客户可以有多个服务员和餐桌如果他们在吧台和桌子之间移动，则可以通过支付或转移items|92134|来处理每个过渡|92135|您还需要一个内置的工作流(新订单、已完成、更新、已关闭和已支付)...|92136|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I think an identification of objects needs to take place prior to any coding (resist the urge to code). Some objects include (some already identified):

<ul>
<li>table</li>
<li>waiter</li>
<li>item (pre-defined list of standard menu items along with ability for daily specials and special order)</li>
<li>order - grouping of items - could be more than one order per table, a client can have multiple waiters and tables if they move from bar to table, each of those transitions could be handled by paying or transferring the items</li>
</ul>

You also need a workflow built in (new order, fulfilled, update, closed and paid)...

What would be the best way to structure orders for a restaurant (available languages are php and javascript)? Since there are multiple tables (the ones you keep things on...), I thought of using objects in javascript. But I am quite new to javascript and absolutely new to OOP, so I'm not sure whether this is the best solution, and whether my design is actually ok. Here is what I have come up with:

<pre><code>var order = {
 id: 0,
 table: 0,
 number_of_items: 0,
 item: {
 name: "",
 quantity: 0,
 unit_price: 0
 },
 total: 0
};
</code></pre>

Structure of orders in restaurant

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

为餐厅组织订单的最佳方式是什么(可用的语言是php和javascript)？因为有多个表(用来保存东西的表)，所以我想到了在javascript中使用对象。但是我对javascript和OOP都是新手，所以我不确定这是不是最好的解决方案，我的设计是否还可以。下面是我的想法：var order = {    id: 0,...

问食肆的订单结构
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问食肆的订单结构EN