We need a new coffee-table book.
我们需要一本可以摆在客厅的。
A coffee table book is also a good idea.
送放在咖啡桌上的书也是一个好主意。
你的书在桌子上。
Your book is on the dressing table.
你的书在梳妆台上。
She laid the book down on the table.
她把书放在桌上。
The book lay open on the table.
书摊开在桌子上。
I'd like to book a table for two for 8 o'clock tonight.
我想订一张今晚8点钟的二人餐桌。
The math book is not on the table.
数学书不在桌子上。
把书放在桌上。
Why restrict the table to only two keywords per book?
为什么要将这个表限制为每本书只有两个关键字？
But, you could decide to index book prices as VARCHAR, as shown in Table 3.
但是，也可以将书籍价格作为VARCHAR进行索引，如表3所示。
Listing 2 shows a simple database access class for the book table.
清单2显示了图书表的简单的数据库访问类。
我的书在桌子上。
Open the schedule book on the first page and copy the table from Fig. 2.
打开日程笔记，把下面的表2复制到第一页。
Indeed, the relationship between Book and Author goes beyond the simple join table.
确实如此，Book和Author之间的关系已经超出了简单连接表的范围。
And this is taken from your book, Table 1.3.
这是从你们书本上摘取下来的，图表3。
The book object represents a row in the book data table.
Book对象代表图书数据表中的行。
Book early if you want a good table.
如果你想要一张好位子的话，及早去预订。
也许我们应该先订一张桌。
We should book a table at the restaurant.
我们应该在餐馆预订位子。
You can do as you please, but I shall keep my book on the table here and read a little every morning as soon as I wake, for I know it will do me good and help me through the day.
你们爱怎样我不管，但我要把书放在这张桌上，每天早上一醒来就读一点，因为我知道，这样会有好处，它将伴我度过每一天。
It's Dad's seat, according to the book about table manners.
根据餐桌礼仪的书，这应该是爸爸的位置。
A Hello! Can I book a table in the restaurant for tomorrow evening, please?
我能在餐馆预订一张桌子吗？明晚的。
书在桌子上。
你的书在桌子上吗？
So, in the case of the book table, there is a primary key field called book_id.
所以，在book表这个示例中，有一个主键字段叫做book_id。
I would like to book a table for four for next Wednesday, December 23.
我想订一张四人桌，12月23日也就是下星期三。
I would like to book a table for four for next Wednesday, December 23.
我想订一张四人桌，12月23日也就是下星期三。
应用推荐