Getting null from JPA query in Spring Boot

I have been getting null for my JPA queries in this Spring Boot Project. This is the project:

Entity:

@Entity
public class Admin {
	
	@Id
	private String login;
	
	@Column
	private String Password;
	public String getLogin() {
		return login;
	}
	public void setLogin(String login) {
		this.login = login;
	}
	public String getPassword() {
		return Password;
	}
	public void setPassword(String password) {
		Password = password;
	}

Repository:

@Repository
public interface AdminRepository extends JpaRepository<Admin, String> {
	
	@Query(value = "SELECT Password FROM Admin WHERE login = :login ", nativeQuery = true)
    String  getp(@Param("login") String login);

Controller:

@Controller
public class AdminController {
	
	@Autowired
	AdminRepository adminRepo;
	
	@RequestMapping("/")                     
    public String home() {
        return "index";           
    }
	
	@RequestMapping("/adminlogin")
	public String adminlogin(Model m) {
		m.addAttribute("command", new Admin());
		return "adminlogin";
	}
	
	@RequestMapping("/alogin")    
    public String login(@RequestParam String login,@RequestParam String password,Model m){    
    	String p = adminRepo.getp(login);
    	
    	if(password.equals(p)) {
    		return "admin";
    	}
    	else {
        return "afail";}
    }
}

I have used same structure and query in many projects before but this is happening for first time. All the queries both inbuilt queries and the native queries that I wrote are giving null but the same queries in the database shows that it is populated.

I have no idea why this is happening, If any one have any thought, please, feel free to share.

I cracked the problem. As I mentioned before that I have used same method in many other projects and it always used to work, so, there wasn't a reason that it wouldn't work this time, that is, if I didn't do something wrong, something different this time.

My usual practice is to first create a entity then the repository then I run the application which creates the table in the database, only after which I create the controller and the user Interface.

What happened this time was that I accidentally ran the application right after I created the entity, which resulted in the creation of the table in database. At the time I thought it was fine and didn't paid any attention to it, only now I realize the table and the repository were not connected. I then dropped the table and ran the app to create it again and it worked like charm.

So here is the conclusion:If the repository is created after the table, the queries will not go through. Only after the repository is created, the table must be created.