and foreign key joins will be more expensive. That being said, here is how you can use non-integer pks in peewee. from peewee import Model, PrimaryKeyField, VarCharColumn class UUIDModel(Model): #

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 2013-01-16 08:16:59.844560+00:00 Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to

limit_choices_to causes errors due to excessively long URLs if you have many thousands of users (the PKs are all included in the URL of the popup window). For this reason, we only apply this limit if the

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 4b678b301dfd8a4e0dad910de3ae245b Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 2013-01-16 08:16:59.844560+00:00 Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 2013-01-16 08:16:59.844560+00:00 Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 4b678b301dfd8a4e0dad910de3ae245b Referential fields are again represented by the PK or sequence of PKs. All data is now dumped with Unicode. If you need the previous behavior, pass allow_unicode=False

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json. For example, if you have some 4b678b301dfd8a4e0dad910de3ae245b Referential fields are again represented by the PK or sequence of PKs. All data is now dumped with Unicode. If you need the previous behavior, pass allow_unicode=False

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json [https://docs.python.org/3/library/json 2013-01-16 08:16:59.844560+00:00 Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to

pk="47"> This example links the given user with the permission models with PKs 46 and 47. Control characters If the content to be serialized contains control characters that are ManyToMany- relations are serialized for the model that defines them and are represented as a list of PKs. Be aware that not all Django output can be passed unmodified to json [https://docs.python.org/3/library/json 2013-01-16 08:16:59.844560+00:00 Referential fields are again represented by the PK or sequence of PKs. Natural keys The default serialization strategy for foreign keys and many-to-many relations is to