··
44
·
2024-10-06 16:33

喝咖啡会导致骨质疏松吗?

咖啡含有不利于钙质吸收的草酸,以及增加尿钙流失的咖啡因,但也含有钾元素,可以阻止钙的流失。

如担心骨质疏松,建议选择纯度高、杂质少、来自天然矿物的碳酸钙补充剂。碳酸钙含钙量高,易被人体吸收,和镁锰锌铜等多种营养素搭配摄入,协同帮助钙沉淀,预防骨质疏松。

PS:建议少喝咖啡,不要依赖于咖啡来提神。不然咖啡上瘾,不喝浑浑噩噩,喝了立刻神清气爽🤣。

0 人喜欢

Add a comment
Comments

There is no comment, let's add the first one.

弦圈热门内容

Django change an existing field to foreign key

I have a Django model that used to look like this:class Car(models.Model): manufacturer_id = models.IntegerField()There is another model called Manufacturer that the id field refers to. However, I realized that it would be useful to use Django's built-in foreign key functionality, so I changed the model to this:class Car(models.Model): manufacturer = models.ForeignKey(Manufacturer)This change appears to work fine immediately, queries work without errors, but when I try to run migrations, Django outputs the following:- Remove field manufacturer_id from car - Add field manufacturer to carDoing this migration would clear all the existing relationships in the database, so I don't want to do that. I don't really want any migrations at all, since queries like Car.objects.get(manufacturer__name="Toyota") work fine. I would like a proper database foreign key constraint, but it's not a high priority.So my question is this: Is there a way to make a migration or something else that allows me to convert an existing field to a foreign key? I cannot use --fake since I need to reliably work across dev, prod, and my coworkers' computers.内容来源于 Stack Overflow, 遵循 CCBY-SA 4.0 许可协议进行翻译与使用。原文链接:Django change an existing field to foreign key

Get connected with us on social networks! Twitter

©2024 Guangzhou Sinephony Technology Co., Ltd All Rights Reserved