[jira] Closed: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan closed DERBY-623: - Fix Version: 10.2.0.0 Resolution: Fixed Closing the issue. No problems reported regarding the fix. Derby monitor accesses two system properties

[jira] Created: (DERBY-1122) Improve base JUnit testing classes

Improve base JUnit testing classes -- Key: DERBY-1122 URL: http://issues.apache.org/jira/browse/DERBY-1122 Project: Derby Type: Task Components: Test Versions: 10.3.0.0, 10.2.0.0 Reporter: Kristian Waagan Priority:

Re: [jira] Updated: (DERBY-919) improve pattern for setting up junit tests

Myrna van Lunteren wrote: I had just downloaded v1.tar...I normally work on windows, so I have to do some moving around to different machines to get tar files unraveled. Is it bad to ask for a jar in future? Sure, I'll use zip (jar) the next time :) Just to spread the word, tar is easily

[jira] Commented: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=comments#action_12370797 ] Øystein Grøvlen commented on DERBY-1058: Patch looks good. I have verified that the added test fails without the fix and succeeds with the fix. However, derbyall

Re: [jira] Created: (DERBY-1122) Improve base JUnit testing classes

Maybe a first step would be to have the SURTest depend on this new class. I understand Andreas had tested this? Myrna On 3/17/06, Kristian Waagan (JIRA) derby-dev@db.apache.org wrote: Improve base JUnit testing classes--Key: DERBY-1122 URL:

Re: [jira] Updated: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

[EMAIL PROTECTED] wrote: Deepa Remesh [EMAIL PROTECTED] writes: On 3/16/06, Dyre Tjeldvoll (JIRA) derby-dev@db.apache.org wrote: [ http://issues.apache.org/jira/browse/DERBY-1093?page=all ] Dyre Tjeldvoll updated DERBY-1093: -- Attachment:

Re: [jira] Created: (DERBY-1122) Improve base JUnit testing classes

Myrna van Lunteren wrote: Maybe a first step would be to have the SURTest depend on this new class. I understand Andreas had tested this? Yes, I will submit a patch for this. Andreas Myrna On 3/17/06, *Kristian Waagan (JIRA)* derby-dev@db.apache.org mailto:derby-dev@db.apache.org

[jira] Updated: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ] Dyre Tjeldvoll updated DERBY-1093: -- Attachment: derby-1093.v1.diff derby-1093.v1.stat derbyall_report.txt I have attached a patch (derby-1006.v1.*) for this.

Re: [jira] Updated: (DERBY-1105) derbyall failures due to change in exception type

Thanks for suggesting. I will create another jira issues for this. But I won't be able work on it for some time. Will pick the issue as soon as i can. anurag Myrna van Lunteren wrote: Hi, I apologize for not paying closer attention to this bug sooner...I only realized the effect when david

[jira] Updated: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ] Dyre Tjeldvoll updated DERBY-1093: -- Other Info: [Patch available] Make DatabaseMetaData.getProcedures() JDBC4 compliant - Key:

[jira] Commented: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

[ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12370800 ] Dyre Tjeldvoll commented on DERBY-1093: --- There is a typo in my attachment comment: 'derby-1006' should be 'derby-1093'. Sorry about the confusion. Make

Regression Test Failure! - Derby 386413 - Sun DBTG

[Auto-generated mail] *Derby* 386413/2006-03-16 19:45:55 CET *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 5643638 0 103.67% CYGWIN_NT-5.1_i686-unknown 2643641 0 116.81%

[jira] Created: (DERBY-1123) Derby Reference Manual - SYSCS_UTIL.SYSCS_CHECK_TABLE

Derby Reference Manual - SYSCS_UTIL.SYSCS_CHECK_TABLE - Key: DERBY-1123 URL: http://issues.apache.org/jira/browse/DERBY-1123 Project: Derby Type: Bug Components: Documentation Versions: 10.1.2.3

[jira] Updated: (DERBY-1123) Derby Reference Manual - SYSCS_UTIL.SYSCS_CHECK_TABLE

[ http://issues.apache.org/jira/browse/DERBY-1123?page=all ] Halley Pacheco de Oliveira updated DERBY-1123: -- Attachment: SYSCS_CHECK_TABLE.diff Diff file to correct the paragraph (svn diff) Derby Reference Manual -

[PATCH] add cleanup to derbyStress.java

Hi, Attached is a patchfor the test jdbcapi/derbyStress.java - it adds a cleanUpTest line. Without this cleanup line, the test causes failure in NullSQLText.java which gets run after in remote server configuration. Tested this test with embedded and DerbyNetClient frameworks, and ran the

Re: [jira] Created: (DERBY-1122) Improve base JUnit testing classes

Myrna van Lunteren wrote: Maybe a first step would be to have the SURTest depend on this new class. I understand Andreas had tested this? Yes. I also have some a test using the new base classes (will submit soon). I created the issue with tasks like the following in mind: * add support

[jira] Commented: (DERBY-942) Add JDBC4 Ease of Development Support

[ http://issues.apache.org/jira/browse/DERBY-942?page=comments#action_12370813 ] Anurag Shekhar commented on DERBY-942: -- jdbc4/TestDbMetaData ois failing because message has changed after 1061 fix. This will change again after 1059 is commited. I will

[jira] Commented: (DERBY-1059) call to stored procedure with out params fails in embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1059?page=comments#action_12370814 ] Anurag Shekhar commented on DERBY-1059: --- Many of the Unimplemented method use class introduced in newer version of jdbc4.0. So mving them in base class will make it

[jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan updated DERBY-1097: --- Attachment: StatementTest.java-v1 StatementTestSetup.java-v1 Updated tests to run with the new base JUnit test classes. Had to rename

Re: Soft Upgrade question

Instead of using export import of data to a new engine, users can restore from the backup on the same version of the engine at diffent location and then do the testing by setting derby.database.allowPreReleaseUpgrade=true I tried to find a description of this property, but was not able

Re: Question about Grant/Revoke

Satheesh Bandaram wrote: No... Default authorization model in Derby 10.2 is still legacy mode.. So if you create a database without setting sqlAuthorization property, you shouldn't be able to do GRANT/REVOKE. Only if you have the property set to true, SQL authorization would be enforced. This

Re: regression ?! all tests in jdbcapi fails for me

Andreas Korneliussen [EMAIL PROTECTED] writes: I did a svn up (to rev 386640.), and all tests fail in jdbcapi. Everything ran fine before the update. Then I did a clean checkout, and compiled and built new jar files. All tests in jdbcapi fails. I have not run other suites. Individual test

Re: regression ?! all tests in jdbcapi fails for me

Andreas Korneliussen wrote: I did a svn up (to rev 386640.), and all tests fail in jdbcapi. Everything ran fine before the update. Then I did a clean checkout, and compiled and built new jar files. All tests in jdbcapi fails. I have not run other suites. Individual test runs also fail with

Upgrade testing

Can someone point me at a primer which describes how developers test soft and hard upgrade? There is some customer-oriented discussion of upgrade in the Developer's Guide and on the Wiki (at http://wiki.apache.org/db-derby/UpgradingTen). But I can't find any pointers on the testing web page

Re: Upgrade testing

On 3/17/06, Rick Hillegas [EMAIL PROTECTED] wrote: Can someone point me at a primer which describes how developers test soft and hard upgrade? There is some customer-oriented discussion of upgrade in the Developer's Guide and on the Wiki (at http://wiki.apache.org/db-derby/UpgradingTen). But I

Re: regression ?! all tests in jdbcapi fails for me

So I guess something must be off with your build or run environment. I built Derby with ant clobber ant buildsource ant testing ant buildjars. I use the 's beacuse I have had problems combining build targets on the same ant command line before. Thank you for the help figuring this

Re: regression ?! all tests in jdbcapi fails for me

Andreas Korneliussen [EMAIL PROTECTED] writes: This classpath caused all tests in jdbcapi to fail for me: Java classpath:

[jira] Commented: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

[ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12370849 ] Kathey Marsden commented on DERBY-1093: --- Please wait to commit this patch until the current issues with ugprade and metadata have been identified and there is

[jira] Commented: (DERBY-1114) derbynet/testSecMec.java fails intermittently and test exits mysteriously when server is shutdown as part of the testrun.

[ http://issues.apache.org/jira/browse/DERBY-1114?page=comments#action_12370850 ] Bryan Pendleton commented on DERBY-1114: Sunitha suggested removing the RunTest harness from the environment to rule that theory in or out. So I ran the test using

[jira] Commented: (DERBY-942) Add JDBC4 Ease of Development Support

[ http://issues.apache.org/jira/browse/DERBY-942?page=comments#action_12370855 ] Rick Hillegas commented on DERBY-942: - Hi Anurag, Thanks for the explanation. I have upgraded to mustang build 76 and that indeed fixed the TestQueryObject problem.

Re: Regression Test Failure! - Derby 386413 - Sun DBTG

Don't think my changes to address grantRevokeDDL failure have been picked up in this test cycle... I will confirm tomorrow if my changes addressed this failure or not. Satheesh [EMAIL PROTECTED] wrote: [Auto-generated mail] *Derby* 386413/2006-03-16 19:45:55 CET *derbyall* Failed TestsOK

[jira] Commented: (DERBY-1116) Define a minimal acceptance test suite for checkins

[ http://issues.apache.org/jira/browse/DERBY-1116?page=comments#action_12370866 ] David Van Couvering commented on DERBY-1116: The approach I was thinking of employing here is to modify RunTest to report the time to run each test (if it doesn't

Re: Question about Grant/Revoke

Oystein Grovlen - Sun Norway wrote: Satheesh Bandaram wrote: At some time in the future when GRANT/REVOKE support is more complete, would it be possible to have some way to turn on SQL authorization automatically when GRANT/REVOKE is used for the first time? I think that could improve

[jira] Commented: (DERBY-1059) call to stored procedure with out params fails in embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1059?page=comments#action_12370867 ] David Van Couvering commented on DERBY-1059: OK, seems reasonable. I'll work on committing this. call to stored procedure with out params fails in embedded

Re: Soft Upgrade question

Satheesh Bandaram wrote: I find current behavior inconvinient... I am trying to understand why Derby doesn't allow soft-upgrade from previous releases. Regardless of whether we provide a mechanism allow soft upgrade, I think that databases that have been modified by alpha software should

Re: [jira] Updated: (DERBY-919) improve pattern for setting up junit tests

Hi, Kristian. I am not sure I understand why you don't just use svn diff to build your patch, rather than posting individual source files or zipping/jarring/tarring/whatevering them up. Is there a reason you don't want to use svn diff? It makes it *very* easy to apply, it's a single file,

Re: regression ?! all tests in jdbcapi fails for me

Dag H. Wanvik wrote: Andreas Korneliussen [EMAIL PROTECTED] writes: This classpath caused all tests in jdbcapi to fail for me: Java classpath:

[jira] Commented: (DERBY-1116) Define a minimal acceptance test suite for checkins

[ http://issues.apache.org/jira/browse/DERBY-1116?page=comments#action_12370873 ] Rick Hillegas commented on DERBY-1116: -- At the end of the day, we want to end up with a basket of tests which 1) covers Derby features and 2) doesn't take too long to

[jira] Commented: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=comments#action_12370874 ] David Van Couvering commented on DERBY-953: --- Sorry, I missed that about getConnection(). But my point still stands, we shouldn't use exceptions for making decisions

[jira] Commented: (DERBY-1116) Define a minimal acceptance test suite for checkins

[ http://issues.apache.org/jira/browse/DERBY-1116?page=comments#action_12370875 ] Satheesh Bandaram commented on DERBY-1116: -- I am not sure picking fastest tests is the way to go for derbymats. May be we could look for tests that actually cought

Re: iapi.services.info sealing problem (was Re: regression ?! all tests in jdbcapi fails for me)

OK, I'll work on fixing this. Let me think about it a bit. David Andrew McIntyre wrote: On 3/17/06, Andreas Korneliussen [EMAIL PROTECTED] wrote: /snip a whole bunch of stuff Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:

[jira] Resolved: (DERBY-1117) SQLException can lose stacktrace in some cases.

[ http://issues.apache.org/jira/browse/DERBY-1117?page=all ] David Van Couvering resolved DERBY-1117: Resolution: Fixed Submitted, revision 386710. Includes a new test that verifies chaining works correctly, both with getCause() and

[jira] Created: (DERBY-1125) Getting security exception because classes in iapi.services.info have been added to derbyclient.jar

Getting security exception because classes in iapi.services.info have been added to derbyclient.jar --- Key: DERBY-1125 URL: http://issues.apache.org/jira/browse/DERBY-1125

[jira] Commented: (DERBY-1126) SanityState.java is not being removed

[ http://issues.apache.org/jira/browse/DERBY-1126?page=comments#action_12370886 ] David Van Couvering commented on DERBY-1126: It looks like this isn't about removing the file, but setting the svn:ignore property for the new location of

[jira] Resolved: (DERBY-1077) [doc] Add relationship table for Developer's Guide

[ http://issues.apache.org/jira/browse/DERBY-1077?page=all ] Jean T. Anderson resolved DERBY-1077: - Resolution: Fixed Committed patch devguidereltable_no_conflicts.diff, revision 386714. Modified files: $ svn commit Sending

[jira] Resolved: (DERBY-1126) SanityState.java is not being removed

[ http://issues.apache.org/jira/browse/DERBY-1126?page=all ] David Van Couvering resolved DERBY-1126: Resolution: Fixed Resolved, revision 386731 SanityState.java is not being removed - Key:

[jira] Updated: (DERBY-690) Add scrollable, updatable, insensitive result sets

[ http://issues.apache.org/jira/browse/DERBY-690?page=all ] Fernanda Pizzorno updated DERBY-690: Attachment: derby-690-v6.diff derby-690-v6.stat Thank you for looking into the patch Øystein. Here is a new patch a answer to Øystein's

Re: Question about Grant/Revoke

So if I put derby.database.sqlAuthorization=true in the derby.properties file then the command like this should execute without error message? ij connect 'jdbc:derby:grntdb;create=true' user 'mkutty'; ij create table tab1(i int, j int); 0 rows inserted/updated/deleted ij grant select on tab1 to

[jira] Updated: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)

[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ] Jeff Levitt updated DERBY-1057: --- Attachment: derby1057_devguide.diff derby1057_devguide_html.zip The patch I am attaching (derby1057_devguide.diff) complements Eric Radzinski's

Regression Test Failure! - TinderBox_Derby 386710 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 386710/2006-03-17 21:52:24 CET *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1644643 0 114.23% Solaris 10 1/06 s10x_u1wos_19a X86 32bits Details in

[jira] Commented: (DERBY-1125) Getting security exception because classes in iapi.services.info have been added to derbyclient.jar

[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12370904 ] David Van Couvering commented on DERBY-1125: OK, to be clear, what happened was not that I included the iapi/services/info package, that has been there for a

[jira] Commented: (DERBY-942) Add JDBC4 Ease of Development Support

[ http://issues.apache.org/jira/browse/DERBY-942?page=comments#action_12370907 ] Anurag Shekhar commented on DERBY-942: -- Hi Rick jdbc4/TestDbMetaData.java is not part of this patch actulally its already in and failing in nightly runs

[jira] Commented: (DERBY-942) Add JDBC4 Ease of Development Support

[ http://issues.apache.org/jira/browse/DERBY-942?page=comments#action_12370908 ] Anurag Shekhar commented on DERBY-942: -- Hi Rick jdbc4/TestDbMetaData.java is not part of this patch actulally its already in and failing in nightly runs

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12370910 ] David Van Couvering commented on DERBY-1097: There is a jdbc4 suite. You can add any JUnit test to a suite using the .junit extension (e.g. StatementTest.junit).

Re: [jira] Commented: (DERBY-668) SysInfo does not print the right information when Derby is not loaded through the classpath.

Andrew McIntyre (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-668?page=comments#action_12370766 ] Andrew McIntyre commented on DERBY-668: --- Hi Bryan, the latest patch for this looks good to me. I would say go ahead and commit when you

[jira] Commented: (DERBY-1125) Getting security exception because classes in iapi.services.info have been added to derbyclient.jar

[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12370911 ] Andrew McIntyre commented on DERBY-1125: I agree, option 1 is the way to go. I remembered after you brought it up in option 3 above that currently the code is

[jira] Resolved: (DERBY-422) Create a new sample database for use in examples in the manuals

[ http://issues.apache.org/jira/browse/DERBY-422?page=all ] Andrew McIntyre resolved DERBY-422: --- Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 386767. Create a new sample database for use in examples in the manuals

Re: [jira] Commented: (DERBY-668) SysInfo does not print the right information when Derby is not loaded through the classpath.

On 3/17/06, Bryan Pendleton [EMAIL PROTECTED] wrote: Thanks Andrew! If anybody else is intending to review DERBY-668, please let me know. Have you tried running it with the security manager enabled? It provides the following puzzling result: Testing for presence of all Derby-related

Re: Upgrade testing

Rick Hillegas wrote: Can someone point me at a primer which describes how developers test soft and hard upgrade? There is some customer-oriented discussion of upgrade in the Developer's Guide and on the Wiki (at http://wiki.apache.org/db-derby/UpgradingTen). But I can't find any pointers on

Re: Soft Upgrade question

Kathey Marsden wrote: Satheesh Bandaram wrote: I find current behavior inconvinient... I am trying to understand why Derby doesn't allow soft-upgrade from previous releases. Regardless of whether we provide a mechanism allow soft upgrade, I think that databases that have been

[jira] Resolved: (DERBY-820) path name incorrect in simple example doc

[ http://issues.apache.org/jira/browse/DERBY-820?page=all ] Andrew McIntyre resolved DERBY-820: --- Fix Version: 10.2.0.0 Resolution: Fixed Assign To: Andrew McIntyre Marking this as fixed. With DERBY-422, I added the toursdb database in

[jira] Resolved: (DERBY-1059) call to stored procedure with out params fails in embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1059?page=all ] David Van Couvering resolved DERBY-1059: Resolution: Fixed Submitted revision 386773 call to stored procedure with out params fails in embedded driver

Re: javadoc warnings.

I see two javadoc warnings in the current trunk: [javadoc] C:\derby\src\java\client\org\apache\derby\jdbc\ClientBaseDataSource.java:813: warning - Tag @see: can't find getUpgradedSecurityMechanism() in org.apache.derby.jdbc.ClientBaseDataSource [javadoc]

Re: Upgrade testing

Thanks, Kathey. I agree it's crucial to verify that changes you make don't impact upgrade, and that this should be part of derbyall. I think it's great Deepa is doing this work. I will try to look at and review the patch, although this is not my area of expertise. David Kathey Marsden

Signal to noise on derby-dev

I don't know if any of you have noticed, but it's getting a bit thick out there on this list. I have heard that the Apache Way is to maintain a single list for a project regardless of how big it is. But has anybody talked to the veterans over at other big projects like httpd or Tomcat to get

[jira] Updated: (DERBY-962) Upgrade default security mechanism in client to use encrypted userid password if client can support it.

[ http://issues.apache.org/jira/browse/DERBY-962?page=all ] Sunitha Kambhampati updated DERBY-962: -- Attachment: d962_javadoc.diff.txt d962_javadoc.diff.txt patch to fix javadoc warnings in ClientBaseDataSource. I ran javadoc and I did a

Regression Test Failure! - TinderBox_Derby 386765 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 386765/2006-03-18 00:22:49 CET *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1644643 0 115.59% Solaris 10 1/06 s10x_u1wos_19a X86 32bits Details in

Re: Soft Upgrade question

Daniel John Debrunner wrote: So if soft upgrade with alpha is run against an existing database are you saying that database should not longer be accessible by any released version of Derby? Yes I think this is best. Once you upgrade to the pre-release version, you cannot go back to 10.1 or up

Re: Regression Test Failure! - TinderBox_Derby 386765 - Sun DBTG

I think the test should be listed as .junit in the suite. Myrna On 3/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: [Auto-generated mail]*TinderBox_Derby* 386765/2006-03-18 00:22:49 CET*derbyall*FailedTestsOKSkipDuration Platform ---*Jvm:

[jira] Commented: (DERBY-962) Upgrade default security mechanism in client to use encrypted userid password if client can support it.

[ http://issues.apache.org/jira/browse/DERBY-962?page=comments#action_12370931 ] Kathey Marsden commented on DERBY-962: -- Hi Sunitha, Looking at your diff I understand why the first @see was taken out because it was not in a javadoc comment, but these

Re: Signal to noise on derby-dev

David W. Van Couvering wrote: I don't know if any of you have noticed, but it's getting a bit thick out there on this list. I have heard that the Apache Way is to maintain a single list for a project regardless of how big it is. But has anybody talked to the veterans over at other big

Regression Test Failure! - TinderBox_Derby 386788 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 386788/2006-03-18 02:52:22 CET *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2645643 0 113.66% Solaris 10 1/06 s10x_u1wos_19a X86 32bits Details in

Re: Regression Test Failure! - TinderBox_Derby 386765 - Sun DBTG

That's mine, I'll fix it. David Myrna van Lunteren wrote: I think the test should be listed as .junit in the suite. Myrna On 3/17/06, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: [Auto-generated mail] *TinderBox_Derby*

[jira] Updated: (DERBY-962) Upgrade default security mechanism in client to use encrypted userid password if client can support it.

[ http://issues.apache.org/jira/browse/DERBY-962?page=all ] Sunitha Kambhampati updated DERBY-962: -- Attachment: d962_javadoc.2.diff.txt Thanks Kathey. Please look at this patch (d962_javadoc.2.diff.txt) I ran javadoc and did clobber and ant all

Regression Test Failure! - TinderBox_Derby 386803 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 386803/2006-03-18 05:12:21 CET *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2645643 0 113.01% Solaris 10 1/06 s10x_u1wos_19a X86 32bits Details in