·

A question about smooth invariance of domain

Published at 2024-11-06 19:32:51Viewed 1 times
Academic article
·
Note
Please reprint with source link

My question: Theorem 22.3 (Smooth invariance of domain). Let $U \subset\mathbb{R}^n$ be an open subset, $S \subset\mathbb{R}^n$ an arbitrary subset, and $f : U \rightarrow S$ a diffeomorphism. Then $S$ is open in $\mathbb{R}^n$.

I can't understand why the set $S$ is not automatically open in $\mathbb{R}^n$. The mapping is a diffemorphism, which means it is continuous in both directions, so $S$ is open.

Answer: All you know a priori, is that open sets $V$ of $U$ satisfy: $f(V)$ is open in $S$, not that $f(V)$ is open in $\mathbb{R}^n$. So, $f(U)=S$ is open in $S$. The claim is then that $f(U)=S$ is actually open in $\mathbb{R}^n$, which is not the same thing and is not automatic. It requires proof.


This speaks of an important blind spot of open sets in topology, i.e. openness is relative. In particular, when considering some subset of a topological space, you should figure out if it is open in the subset, or in the ambient space.

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