On 1 February 2012 11:07, amvis wrote:
>
>
> Colin simply i am saying here the truncate means, remove all the rows. so
> after the truncate, it should start from id 1.
> But now the default id start from the next to old one( that means
> 173,174.).
Yes, that is the way it works. If yo
On Wed, Feb 1, 2012 at 10:22 AM, amvis wrote:
> Thanks for the reply.
>
> Exactly what going on here is now,after the execution of one insertion
> some amount of data will insert, around 172 rows, but after i truncate the
> tables, again when i execute that operation, the row count starting fro
On 1 February 2012 09:22, amvis wrote:
Please don't top post, it makes it difficult to follow the thread.
Insert your reply at appropriate points in previous message. Thanks.
> Thanks for the reply.
>
> Exactly what going on here is now,after the execution of one insertion
> some amount of da
Thanks for the reply.
Exactly what going on here is now,after the execution of one insertion
some amount of data will insert, around 172 rows, but after i truncate the
tables, again when i execute that operation, the row count starting from
173... i think that happens of new object creation f
On 1 February 2012 07:56, amvis wrote:
>
> tran
> =Transaction.select("transactions.id,transactions.user_id,transactions.branch_id,transactions.customer_id,transactions.membership_type_id,transactions.bill_amount,transactions.bill_date")
> treport = TransactionReport.new
> puts "from report"
>
tran
=Transaction.select("transactions.id,transactions.user_id,transactions.branch_id,transactions.customer_id,transactions.membership_type_id,transactions.bill_amount,transactions.bill_date")
treport = TransactionReport.new
puts "from report"
tran.each do |u|
bs = *TransactionReport*.ne
6 matches
Mail list logo
