user2995: I have 10 btc on address A.
Using raw transaction, I send 5btc from A to B and set the change address as A itself. Now because the transaction from A to B is not confirmed I can't spend the remaining 5 btc.
But I saw that the QT wallet can do this. Ex:
I have 10 btc on address A. I send 5btc to B. The wallet creates a new address C and sets it as the change address. Then I try using the 5 btc on the wallet and it works. It allows me to send from address C. 
1) Is the wallet using unconfirmed outputs as inputs here?
2) If so, how is it doing this and how can I do it using raw transactions?
3) If not, what's going on here?

user6388: It looks like Bitcoin QT is able to reference it's own unconfirmed transactions, which is kind of dangerous. Consider this: 
The first transaction (A to B) might arrive in the block chain after the second (C to ...) or it might not arrive at all. In this case, the second transaction will not go through because it won't be valid until the first one happens. Even though the second transaction exists within Bitcoin QT, it probably doesn't get sent out until the first goes through.
If you want to do this with raw transactions, you can create both transactions at the same time, just know that the second one will be invalid (and thus rejected by the block chain) until the first one goes through. 

user6150: Bitcoin-QT treating the change as okay to spend depends on the client itself having created it within itself. Creating transaction with createrawtransaction change as unconfirmed. Bu sendfrom not.

user403: 
Is the wallet using unconfirmed outputs as inputs here?

Yes.

If so, how is it doing this

Except for coinbase transactions, transactions are independent of blocks. A transaction spending an unconfirmed input looks exactly the same as a transaction spending a confirmed input.
It's safe for Bitcoin-Qt to spend unconfirmed change because it knows that the input is valid and will be confirmed at some point (though probably slowly). It would not be safe for Bitcoin-Qt to spend unconfirmed inputs that it did not itself create because they might never confirm, resulting in permanently tied-up funds. (Very old versions of Bitcoin made this mistake, but it was corrected after widespread issues.)

how can I do it using raw transactions?

You can create the transaction with createrawtransaction normally, but you'll need to give signrawtransaction some extra info about the unconfirmed transaction in its second parameter.

2995: <p>I have 10 btc on address A.</p>

<p>Using raw transaction, I send 5btc from A to B and set the change address as A itself. Now because the transaction from A to B is not confirmed I can't spend the remaining 5 btc.</p>

<p>But I saw that the QT wallet can do this. Ex:</p>

<p>I have 10 btc on address A. I send 5btc to B. The wallet creates a new address C and sets it as the change address. Then I try using the 5 btc on the wallet and it works. It allows me to send from address C. </p>

<p>1) Is the wallet using unconfirmed outputs as inputs here?</p>

<p>2) If so, how is it doing this and how can I do it using raw transactions?</p>

<p>3) If not, what's going on here?</p>
 6388: <p>It looks like Bitcoin QT is able to reference it's own unconfirmed transactions, which is kind of dangerous. Consider this: </p>

<p>The first transaction (A to B) might arrive in the block chain after the second (C to ...) or it might not arrive at all. In this case, the second transaction will not go through because it won't be valid until the first one happens. Even though the second transaction exists within Bitcoin QT, it probably doesn't get sent out until the first goes through.</p>

<p>If you want to do this with raw transactions, you can create both transactions at the same time, just know that the second one will be invalid (and thus rejected by the block chain) until the first one goes through. </p>
 6150: <p>Bitcoin-QT treating the change as okay to spend depends on the client itself having created it within itself. Creating transaction with createrawtransaction change as unconfirmed. Bu sendfrom not.</p>
 403: <blockquote>
  <p>Is the wallet using unconfirmed outputs as inputs here?</p>
</blockquote>

<p>Yes.</p>

<blockquote>
  <p>If so, how is it doing this</p>
</blockquote>

<p>Except for coinbase transactions, transactions are independent of blocks. A transaction spending an unconfirmed input looks exactly the same as a transaction spending a confirmed input.</p>

<p>It's safe for Bitcoin-Qt to spend unconfirmed change because it knows that the input is valid and will be confirmed at some point (though probably slowly). It would not be safe for Bitcoin-Qt to spend unconfirmed inputs that it did not itself create because they might never confirm, resulting in permanently tied-up funds. (Very old versions of Bitcoin made this mistake, but it was corrected after widespread issues.)</p>

<blockquote>
  <p>how can I do it using raw transactions?</p>
</blockquote>

<p>You can create the transaction with <code>createrawtransaction</code> normally, but you'll need to give <code>signrawtransaction</code> some extra info about the unconfirmed transaction in its second parameter.</p>
