How did you answer the previous question? Here comes today’s interview question!

Q:

Let hash table length m = 14, hash function H (key) = key % 11. Addr (15)=4, addr(38)=5, addr(61)=6, addr(84)=7;

What is the address of the node with keyword 49 if the conflict is handled with secondary detection and hash?

Post your thoughts and answers in the comments section, and follow me next time.

Previous issues:

The following description of the configuration implications of Spring declarative transactions is incorrect ()

A. Defines A configuration template for declarative transactions

B. Use read-only transactions for get methods

C. SessionFactoy property injection is missing

D. Configure the proxy for the bean that requires transaction management, using parent to reference 込 configuration templates as follows:

<bean id="petBiz" parent="txProxyTemplate">
      <property name="target" ref= "petTarget"/>
</bean>
Copy the code

The answer:

C

The emperor as the object, eunuch as IOC container, when the emperor to choose the concubine to sleep at night, do not have to take care of, as long as to the bed. Eunuchs are fond of according to the emperor (find corresponding dependence or other objects), find the corresponding concubine sent to the emperor bed.

<! -- Configure transaction manager --> <property name="transactionManager"> <! -- Configure transaction properties --> <property name="transactionAttributes">        
<props> 
Copy the code

Declarative transaction management is based on AOP. The essence is to intercept before and after the method, then create or join a transaction before the target method starts, and commit or roll back the transaction after the target method is executed. The biggest advantage of declarative transactions is that they do not need to be managed programmatically. This means that you do not need to mix transaction management code with your business logic code. Instead, you can apply transaction rules to your business logic by declaring them in a configuration file (or by using the @Transactional annotation).