Thumbnails are not really the exact images you deleted. They are just the cached images of extremely low quality which your phone used to show you images with more speed. Your phone save a Thumbnail of image you open in your phone so that next time you open that image, it takes less time. Thumbnails have very small resolution and quality than original. Clearing your cache memory will delete the thumbnails. Usually, phone don't have any automatic thumbnails deletion.

J.D. Mentioned Row Level Security in a comment and it seems very promising for people who need to do what I want but only have SQL to work with. If they post an answer I will give them credit for this question. Though it is possible to create migrations in EFCore that allows for custom SQL to be executed when the database is deployed, it felt forced. But still probably a valid solution https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/operations https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/managing?tabs=dotnet-core-cli https://docs.microsoft.com/en-us/sql/relational-databases/security/row-level-security?view=sql-server-ver15 Based on the new terms in my vocabulary, I found global query filter from EFCore and I went with that. https://docs.microsoft.com/en-us/ef/core/querying/filters Though you do need to be a bit careful with how you set it up. Using required navigation to access entity which has global query filter defined may lead to unexpected results. But in essence it boils down to adding something like this to the code first configuration. modelBuilder.Entity().HasMany(b => b.Posts).WithOne(p => p.Blog).IsRequired(); modelBuilder.Entity().HasQueryFilter(b => b.Url.Contains("fish")); modelBuilder.Entity().HasQueryFilter(p => p.Blog.Url.Contains("fish")); https://www.rubberchickenparadise.com/blog/2020-04-01-handling-row-level-security-with-entity-framework/ , where they discuss injecting user JWT token info into the context to allow personal filtering for an individual. public class Context : DbContext { private readonly IClaimsProvider _claimsProvider; private int UserId => _claimsProvider.UserId; private IEnumerable<int> AccessibleClientIds => _claimsProvider.AccessibleClientIds; public Context(DbContextOptions<Context> options, IClaimsProvider claimsProvider) : base(options) { _claimsProvider = claimsProvider; } ... } modelBuilder.Entity(entity => { entity.HasQueryFilter(x => AccessibleClientIds.Contains(x.Id)); entity.HasKey(x => x.Id); entity.HasMany(x => x.UserClientAccess) .WithOne(x => x.Client) .HasForeignKey(x => x.ClientId); }); modelBuilder.Entity<UserOptions>(entity => { entity.HasQueryFilter(x => x.UserId == UserId); entity.HasKey(x => x.Id); }); https://spin.atomicobject.com/2019/01/29/entity-framework-core-soft-delete/ talks about overriding the default savechanges functionality to always soft delete, but this is not what I want, but some might find it helpful. public override int SaveChanges() { UpdateSoftDeleteStatuses(); return base.SaveChanges(); } public override Task SaveChangesAsync(bool acceptAllChangesOnSuccess, CancellationToken cancellationToken = default(CancellationToken)) { UpdateSoftDeleteStatuses(); return base.SaveChangesAsync(acceptAllChangesOnSuccess, cancellationToken); } private void UpdateSoftDeleteStatuses() { foreach (var entry in ChangeTracker.Entries()) { switch (entry.State) { case EntityState.Added: entry.CurrentValues["isDeleted"] = false; break; case EntityState.Deleted: entry.State = EntityState.Modified; entry.CurrentValues["isDeleted"] = true; break; } } } Eventual implementation I have all the relevant models inherit from Deactivateable to add the property/col to the database. Then because of the simplicity of the filter I simply created this config in the context: foreach (var entity in modelBuilder.Model.GetEntityTypes()) { if (entity.ClrType.IsSubclassOf(typeof(Deactivatable))) { var dateTimeOffsetDefaultValue = new DateTimeOffset(new DateTime(1, 1, 1, 0, 0, 0, 0, DateTimeKind.Unspecified), new TimeSpan(0, 0, 0, 0, 0)); modelBuilder.Entity(entity.ClrType, o => { o.Property(nameof(Deactivatable.DeactivatedDate)).HasDefaultValue(dateTimeOffsetDefaultValue); }); var deactivatedDate = entity.FindProperty(nameof(Deactivatable.DeactivatedDate)).PropertyInfo; var parameterExpression = Expression.Parameter(entity.ClrType); var propertyExpression = Expression.Property(parameterExpression, deactivatedDate); var constExpression = Expression.Constant(dateTimeOffsetDefaultValue); var equalExpression = Expression.Equal(propertyExpression, constExpression); var filter = Expression.Lambda(equalExpression, parameterExpression); modelBuilder.Entity(entity.ClrType).HasQueryFilter(filter ); } } Based on the inspiration from this https://github.com/dotnet/EntityFramework.Docs/issues/2820#issuecomment-803489089 made by https://github.com/stevendarby . I couldn't figure out where they got .Model.FindLeastDerivedEntityTypes from, so I simply chose to iterate the models myself and look at the subclass, based on an idea I saw in a related SO post, which I can no longer find and reference.

It fails because there is a foreign key, not because of integrity: the move is DDL, not DML.

The implementation may be: -- books table CREATE TABLE Ebook (ebook_id INTEGER PRIMARY KEY AUTOINCREMENT, name VARCHAR(255) UNIQUE); -- tags table CREATE TABLE Tags (tag_id INTEGER PRIMARY KEY AUTOINCREMENT, name VARCHAR(255) UNIQUE); -- adjacency table PRAGMA foreign_keys = ON; CREATE TABLE TagsToEbooks (ebook_id INT, tag_id INT, PRIMARY KEY (ebook_id, tag_id), FOREIGN KEY (ebook_id) REFERENCES Ebook (ebook_id) ON DELETE CASCADE ON UPDATE CASCADE, FOREIGN KEY (tag_id) REFERENCES Tags (tag_id) ON DELETE CASCADE ON UPDATE CASCADE); -- Trigger which will delete unused tags after book deletion CREATE TRIGGER delete_unused_tags AFTER DELETE ON Ebook BEGIN DELETE FROM Tags WHERE NOT EXISTS ( SELECT NULL FROM TagsToEbooks WHERE Tags.tag_id = TagsToEbooks.tag_id); END; https://dbfiddle.uk/?rdbms=sqlite_3.27&fiddle=3240437678fe642477e75f07a30affb6

Problem was, the uniform didn't sabotage the server. The button wasn't in shape.

The compiler does not remove itself (not adding the detour to the code) for objects that are created simply through new ones. Yes, 99% of the memory will be returned to the system, but the destructors will not be called. If there's a logic on it, then yo.It is highly desirable that everything that has been allocated clearly through new/malloc be released. If the facility allocates any specific resources to the operating system, it may not release them. And the file descriptors will be closed by the DS. But if it's a stream, there's no guarantee that his internal buffers will be dropped before the file descriptor is closed and the data may be lost.

Question's off!If the project uses Spring Security, each request automatically passes csrf tokens of PUT, PATCH, DELETE should be transmitted through thymeleaf:<form th:method="delete" th:action="@{/feed/1}"> <input type="submit" value="Delete" /> </form> So after the generation, the body of the request looks like:<form method="post" action="/feed/1"> <input type="hidden" name="_csrf" value="беспорядочный набор символов"> <input type="hidden" name="_method" value="delete" wfd_invisible="true"> <input type="submit" value="Delete" /> </form> Thymeleaf generates hidden methods and needs to be resolved. I only know about two ways resolve them:The following bin shall be created in the file marked annotations @Configuration or @SpringBootApplication:@Bean public FilterRegistrationBean hiddenHttpMethodFilter() { FilterRegistrationBean filterRegistrationBean = new FilterRegistrationBean(new HiddenHttpMethodFilter()); filterRegistrationBean.setUrlPatterns(Arrays.asList("/*")); return filterRegistrationBean; } In application.properties add:spring.mvc.hiddenmethod.filter.enabled=true Choose one of the ways and move on to future problems)

Overall, there is no solution. The approximate solution can be made a little different. Don't send bullets that come or don't, but instead, from the application, you're gonna knock on your server periodically. If you haven't knocked on the server for a while, consider it deleted. Although, of course, this may mean that the motto is off, there is no network, the laser clearly banned the annex from launching etc. Use Androids. https://developer.android.com/topic/libraries/architecture/workmanager And for iOS, it looks like an equivalent. https://developer.apple.com/documentation/backgroundtasks ♪ There may be larvae under the ReactNative, which is exactly what these naive libes do.

I found a related question. https://stackoverflow.com/questions/7739144/thread-safety-for-overloaded-operator-new Brief translation.For the built-in operator, the new standard guarantees that it will be thread safe (if it wasn't as long as it's broken...).For users, this is not guaranteedIf you add a code that doesn't eat thread safe, it's gonna be bad.Like this operator.struct Foo { static void * operator new(size_t n) { return ::operator new(n); } // OK }; It's okay.And if there's something to do with it... ♪

Something like that.DROP TABLE IF EXISTS Teachers; DROP TABLE IF EXISTS Subjects; CREATE TABLE Subjects (subject int Primary key, details varchar not null, credit int ); INSERT INTO Subjects (subject,details,credit) VALUES (1111,'Matan',4), (2222,'Biolog',8), (3333,'Leng',3), (4444,'PE',5); CREATE TABLE Teachers (teacher_id int Primary key, last_name varchar(255) Not NULL, group_code varchar(255) not null, hours integer, students integer, subject int References Subjects(subject) ); INSERT INTO Teachers (teacher_id,last_name,group_code,hours,students,subject) values (11,'Tarasuk','pmi27',11,27,1111), (22,'Markiz','pmi21',10,24,4444), (33,'Orst','pmi32',8,3,2222), (44,'Krazy','pmi43',30,20,2222); --удаление не работает DELETE FROM Teachers m USING Subjects sub WHERE sub.subject = m.subject and m.students<25; -- DELETE FROM Subjects sub -- USING Teachers m -- WHERE sub.subject = m.subject and m.students<25; You have a problem with the connection tables.

You have a reaction to the event. change But there's still a need to check what's changed. .checkedIf he is. true Add the tx if false Don't add or remove.... if(activeCheckboxes.checked) { //добавить тест } else { // убрать текст или ничего не делать }

Teachers are a little outdated. Contemporary fashion postulate - the code doesn't have to be "primary" indexes - i.e. indexes not wrapped in smart ribs like unique_ptr and shared_ptr♪If with unique_ptr You can agree unconditionally, he does not make an overhead and works very foreseeable, then shared_ptr It should be treated with caution, because with it resources will flow exactly as without it, but it will have a sense of well-being.

You have a typical mistake that's been discussed a lot of things. You don't copy the list yourself. reference It's him. So all the changes you're making on the same list are on the other list right now because it's one list you have two references.result_user_list = cur_users_list To copy exactly the contents of the list, not just the reference, it is possible to:result_user_list = cur_users_list.copy()

You should do a cycle in the reverse direction, from the end to the beginning, because otherwise, if the elements of the mass are removed immediately in the cycle, they might lead to ConcurrentModificationExceptionalthough in rare cases https://ru.stackoverflow.com/q/540292/191482 or an incorrect disposal occurs, as the cells &apos; indices are replaced after removal.In general, it is possible to:String[] arr = {"ПЕРВЫЙ", "ВТОРОЙ", "ВТОРОЙ", "ТРЕТИЙ", "ЧЕТВЕРТЫЙ", "ПЕРВЫЙ", "ВТОРОЙ", "ПЕРВЫЙ", "ВТОРОЙ", "ПЕРВЫЙ", "ЧЕТВЕРТЫЙ"}; ArrayList<String> list = new ArrayList<String>(Arrays.asList(arr)); String n = "ПЕРВЫЙ"; String s = "ВТОРОЙ"; String w = "ТРЕТИЙ"; String e = "ЧЕТВЕРТЫЙ"; for (int i = list.size() - 1; i >= 0; i--) { if (list.get(i).equals(s) && list.get(i - 1).equals(n)) { list.remove(i); list.remove(i); } } for (int i = 0; i < list.size(); i++) { System.out.println(list.get(i)); } It's twice called here. list.remove(i);Not list.remove(i); list.remove(i - 1); It's because after the challenge, it's the first time. list.remove(i); List indices shall be recalculated as in place i - 1 It's gonna change the index. iThere's more to it than that. It is not possible to remove directly from the mass. Every time, we need to make a copy of the reduced number of elements in which all elements of the previous one will have to be collated in the cycle, with the exception of the element on the said position in the vent of the mass

b = a.replace("a","", 1) Only one driving (first) will be removed.

It's decided that the request for OPTIONS should be processed first:res.statusCode = 200; res.setHeader('Content-Type', 'application/json'); res.setHeader('Access-Control-Allow-Origin', '*'); res.setHeader('Access-Control-Allow-Headers', '*'); res.setHeader('Access-Control-Allow-Methods', '*'); res.end();

Because it's here.// add: while(iterator.hasNext()) { System.out.print(iterator.next() + " "); } You've come to the end.And in an attempt I' removed everything.♪while(iterator.hasNext()) { iterator.next(); iterator.remove(); } iterator.hasNext() Come back. falseAs the terator He's alive.a new one.

In the first case, you havevector<std::vector<T*>*> *values = new vector<vector<T*>*>(1000,new vector<T>(1000, new T())); All 1,000 elements of the first vector will be same index on a vector where 1,000 equal indexes will be stored of the same value type T!In fact, as much as the problem of memorial release will be in the second case, so use it (and without an index):vector<std::vector<T>> values(1000,vector<T>(1000,T{})); If there's any reason why... you need an incision--- well, then...vector<std::vector<T>> *values = new vector<vector<T>>(1000,vector<T>(1000,T())); ... delete values; But I don't see much.The release of memory in the first case, if you fix it, is too big and complicated, one thing makes the whole code meaningless (yes and working with such a structure-- you're confused with undeclarations). Not for that vector:P.S. In the first case, the unnecessary indirect treatment (and not one) is in principle contributing and reducing productivity. ♪ ♪

Turns out it's very simple:await bot.http.remove_reaction(channel_id,message_id,emoji,membe_id)

from getpass import getpass password = getpass()