ibatis executes multiple select statements at a time

As long as you can ensure that the fields in table c are the same every time this statement is executed, then modify it like this.

select , from lybbs_author aouthror , blog_users users , tablename$ c where

and = and =

Just pass your table name in the form of a variable tablename and you're good to go.

As long as you can save the fields in Table C the same every time this statement is executed, then tune it this way.

select , from lybbs_author aouthror , blog_users users , tablename$ c where

and = and =

Just pass in the name of your table as a variable tablename.

Basically agree with the upstairs, I would like to add that the parameter should be in the form of tablename, and $tablename$ is used in hibernet or ibatis in the form of "". And if you need to follow some conditions after where, it's best to use map to pass parameters. The above is complete.

Upstairs is right, update first and then select, but you can't nest update statements between them, so you can only call them twice but you can use batch processing.

Update first, then select, you can use batch operations.

I've tried, but it didn't work, so I'm looking for a high finger as well, but if it's pure ibatis.

private sqlmapclient sqlmap ;

public void dosomething(Argument 1, argument 2 throws sqlexception finally.)

Of course, if you have Spring, you can also combine Spring's iBacatis helper class to operate, and in the new Ibatis version, everything has been handed over to Spring, but it's pretty much the same.

No, I remember that 2 SQL can be executed in mybatis, and ibatis should also be able to. The return value in the first SQL statement can be executed as a condition in the second SQL statement.

select seqno from table where ..for update

update table set seqno = seqno+1

You run the following SQL statement in the database to see how much data is returned.

Pass the value from your DAO layer. Because it is multiple variables, it is necessary to use map to transmit it.

ibatis configuration file writes:

select * from eadept ea where in (#id1##id2##id3##id4#

The inside of the DAO layer is encapsulated with map:

id1","001008");

id2","001009");

id3","001010");

id4","001007");

Then just pass the map over. Try it! Hope it helps!

The documentation on the official website has instructions.

select * from t_blog where id in#

This one doesn't work! Because you're executing multiple statements at the same time! You can only execute it when you do it one by one! Or you can just fix the wrong SQL statement!

Yes! The others succeeded!

I see what you mean.

It's the statement. go statement.

go statement. Right? Only the one that reported the error didn't succeed! Others, if the prompt is successful, it's a success!

It's best to get into the habit of first checking and then triangulation hehe.

If you don't judge, if you don't have a rollback then the execution is successful.

It is the same as the SQL configuration of a single statement, except that when receiving the return, it is received with a list.

You have to execute the two separately and independently, or the two execute together can't stick the ** together!

And you didn't post **, it's hard to judge.

Are they not in a ** segment, a transaction? begin 。。end？ commit ？

Yes, I don't know your specific situation, how to judge.