Nothing here yet.
Nothing here yet.
No blogs yet.
Yes, of course you are right! Unfortunately I can't find the place in article where I said that :) I know that I wrote this: String is a growable, heap-allocated data structure that owns its contents. It is used when you need to modify or own the contents of a string. You can create a String from a string literal using the to_string method or the String::from function. &str is a string slice that points to a sequence of UTF-8 bytes, usually stored elsewhere in memory. It is used when you need to borrow a string without taking ownership of it. You can create a string slice from a string literal using the & operator or the as_str method.
Good article for beginners, where everything is well explained. However it's hard to demonstrate the effectiveness of indexes on such small tables. Normally you wouldn't need an index for a table with less than one thousand records. E.g. In my current job, I have a table with sales (one of many) in which I have at least eighteenth million headers per month. Which means that we have at least a total of 2 592 000 000 headers only. Imagine how many positions, products and payment records we have. And to be honest you need to be extremely careful with indexes. Because they not only increase storage, but degrade overall database performance while data grows. One of the solutions is to move to Hadoop or Data Lake infrastructure or use horizontal scalable databases such as ScyllaDB or CockroachDB.