Recently learned SQL to create the index tuning, but used before the Spring data jpa framework to write a web BBS, framework encapsulates the add and delete, article directly with interface to add and delete, feeling already can't create indexes by the native SQL tuning, then what should I do

CodePudding user response:

Use stored procedures,

CodePudding user response:

Framework and optimization, which is the conflict,
Framework for development, but can't optimize,
Need optimization, please use native SQL or stored procedures to perform,
Don't use a frame for all the things,

CodePudding user response:

Lock means you can create indexes, but if you need to use the index to optimize a function, use native SQL statements,

CodePudding user response:

refer to the second floor of gypsy song response:

frame and optimization, which is the conflict,
Framework for development, but can't optimize,
Need optimization, please use native SQL or stored procedures to perform,
Don't use a frame for everything,

Lock means you can create indexes, but if you need to use the index to optimize a function, use native SQL statements,

CodePudding user response:

reference 4 floor BOWWOB response:

Quote: refer to the second floor of gypsy song response:

frame and optimization, which is the conflict,
Framework for development, but can't optimize,
Need optimization, please use native SQL or stored procedures to perform,
Don't use a frame for everything,

Lock means you can create indexes, but if you need to use the index to optimize a function, use native SQL statements,

Requiring at least complex queries, where need native SQL.