InsertResult to return the primary key's type

[billy1624]

Resolve #103

Special thanks to @acidic9 for providing inspiration on PR #112

[billy1624]

If this passes all tests, I will start re-think about all these trait bounds

sea-orm/src/entity/primary_key.rs

Lines 10 to 18 in 4e5a8d2

	pub trait PrimaryKeyTrait: IdenStatic + Iterable {
	type ValueType: Sized
	+ Default
	+ Debug
	+ Display
	+ PartialEq
	+ IntoValueTuple
	+ TryGetable
	+ FromStr;

[billy1624]

Why I got this error again?
https://github.com/SeaQL/sea-orm/runs/3454985766?check_suite_focus=true#step:6:104

[billy1624]

Why I got this error again?
https://github.com/SeaQL/sea-orm/runs/3454985766?check_suite_focus=true#step:6:104

Okay, it was solved on 4d0c5f0

[tyt2y3]

We need a trait TryFromU64 to replace the use of FromStr

[tqwewe]

We need a trait TryFromU64 to replace the use of FromStr

How would TryFromU64 work with something like UUID? I don't think postgres returns UUID as an integer does it?

[tyt2y3]

I think the Postgres side will fairly ignore that. We were only trying to fix the MySQL side.

[billy1624]

Wow the commit hash starts with 0e0ee0e lolll

[tqwewe]

I'm curious why the trait TryFromU64 is added instead of using From<u64> or TryFrom<u64> 🤔
It seems like this might cover cases for libraries with types that already implement From<u64> / TryFrom<u64>
Sorry if this has already been discussed

[billy1624]

I'm curious why the trait TryFromU64 is added instead of using From<u64> or TryFrom<u64> 🤔
It seems like this might cover cases for libraries with types that already implement From<u64> / TryFrom<u64>
Sorry if this has already been discussed

I think what we have here is not an usual logic of From<u64> or TryFrom<u64>. So, we better not use the conventional std traits.