Why resultset is interface

Hi all,
In JDBC, statement, Resultset, CallableStatement, PreparedStatement interfaces there.
My question is, why they are interfaces but not classes.
If anybody knows, pl. answer to my question.
Thanx and regrads,
srinivas

They are interfaces because they need to be implemented differently (possibly) by each creator of a JDBC driver. The class that does the work for a PreparedStatement in the Sun ODBC-JDBC driver is not the same one that does the work for a PreparedStatement for the Oracle thin client driver.

Similar Messages

Why to use Interface if methods are not implemented??

Hello,
I am having a problem to clearify as, why to use the interfaces which defines only methods and no implementation??
When a class implements an interface the methods are implemented by the class itself, don't you think that the same functionality can be achieved if the class defined the method itself...
The why to use interfaces, just that the same method name can be used by many classes or some other reasons..

did you google on that? There is lots of information I am sure explaining why you code to an interface defined type rather than a class defined type.
However, fundamentally you are correct, classes define their own type. The idea is that you use an interface because it allows you to have more than one implementation. Plus you can more easily change the structure of your program if you later wish if you did not use the class type directly.
You get better answers if you ask in the Patterns forum below.

Why not use interfaces for constants?

Hi,
I have been getting conflicting views about why not use interfaces for constants?
Can anyone shed some light on it?
Piyush

How so?
If the constants are only used in a single classhow
does it help to put them in a separate structute?
(Ignoring the a type safe enumeration of course.)Well, mainly for readability. Suppose that you have a
web application which has a servlet class
"RedirectServlet", which takes a variable to redirect
to a given JSP file. In the JSP files, you want to
create forms which take this servlet as their action.
You could of course put all these "redirect"
constants in the RedirectServlet itself, but then
it's kind of weird that you have to import a
servlet in your jsp file to include these constants
and to be able to write
<form action="servlet/RedirectServlet?key=<%=
RedirectServlet.HOMEPAGE %>> or so.
Instead, you could create an interface called
"RedirectConstants", and then your servlet
RedirectServlet could implement this interface. Then
your JSP can also access these constants via this
interface.
But then again, this is merely a matter of style, I
fully agree that there is never a real _need_ to put
constants in a separate structure if they're only used
in a single class.Are you claiming that your example above is a single class?

Why all are interfaces in JDBC

why all are interfaces in JDBC
If anybody knows the answer tell me plz

Because of encapsulation of major database functionality, such as running queries, processing results, and determining configuration information.
JDBC interfaces is like a plug, where u can plug in any database to your application by adding there respective JDBC Driver.
The JDBC Driver is a set of classes that implement the JDBC interfaces to process JDBC calls and return result sets to a Java application. Thats the magic of encapsulation, we just have to program to the interface rather than the implementation. The implementation might change regularly keeping the interface unchanged and hence our application.
The one of the suggestion of design patterns, is , program to an inteface and not to an implementation.

Why the "hme0" interface is missing?

Hallo! I'm working on a Sun Blade 150 (Solaris 8 4/01). I did a "ifconfig -a" and only see the "lo0" loppback interface and the "eri0" interface.
Why the "hme0" interface is missing?
Edited by: Wolfgang073 on Jan 17, 2010 9:11 AM

Wolfgang073 wrote:
Hallo! I'm working on a Sun Blade 150 (Solaris 8 4/01). I did a "ifconfig -a" and only see the "lo0" loppback interface and the "eri0" interface.
Why the "hme0" interface is missing?
Edited by: Wolfgang073 on Jan 17, 2010 9:11 AM... because for Solaris-ethernet-on-SPARC, the interface name is specific to the chipset that is used for the function.
Your SB150 uses an "ethernet RIO interface" (ERI) on a discrete chipset and does not use hardware for what has often been named "highspeed-media-ethernet" (HME).
The hardware is different, thus the acronym is different.
Others may choose to offer a better description.

Why is the Interface on My MacBookPro stationary but On my G4laptop its Movable?

Why Can't I move the Interface around on My MacBook Pro but I can on My G4 powerbook
Why is it that when I am in Lightroom in my catalog and on my external HD when I am on my daughters Mac Book Pro intel laptop
the lightroom Interface cannot be moved around on the desktop. I can only minimize the page.
but when I put the same catalog up on my G4 powerbook 12" laptop I can see the
entire Lightroom interface with menu bar and I can grab the entire interface and move it around.
this scares me to think that something is wrong with lightroom on the Intel Mac. I worry about it corrupting my catalog that I have worked hard on with importing thousands of images into and would not want to have it not be able to be backed up.
when I am on the intel mac book pro with lightroom, it sometimes will not let me back up my catalog and that makes me think that it is corrupted and not backup able. please someone help me find a reason for this
I am on lightroom 1.2 and been studying on it all summer and fall. thank you out there......
Ken

thank you Jeff, btw, I enjoyed your Luminous Landscape videos with MR , I must have looked at it 50 time! dang!
listen to you at the Photo Expo in NYC but did not stop you to ask a question or say hello
thanks for the help...godfather, KS

Why are the interfaces of PRO APPLICATIONS different, Why not fixed in FCS3

From someone who has been working on macs since 1984, and making my living as a video producer/editor since 1991 using mac:
Back in the first two decades of Apple's existence, all apps had "Universal Tools & Interfaces". An arrow, a crosshair, a timeline.... You get the picture. LiveType, Motion, Soundtrack Pro, Logic, WaveBurner, and DVD Studio ALL have different looking and acting tools and timelines. This unnecessary mess of differing type tools and interfaces goes against the one thing that makes Macs Macs.
My limited mind can only store so much. It can hold LT, FCP, and Logic interfaces, norms, key commands, timeline behaviors. I don't have any more mind space for yet another app's. I got completely confused in SoundTrack today.... Oh that's the fourth App I had to use.... I got an error message "There's not enough brain matter to continue, you can cry, spend an hour re-learning, or just edit the 15 tracks of audio in FCP"
I can't believe it's just me who feels this way. They sell us suite of products, all with differing interfaces and key based tools. You would have thought by this third version they'd make A = pointer or B= Blade or 0 = Rewind in at least two apps.... I hope someone at Apple is trying to fix this horrible situation. I can only hope.... I hope they will still "support" LiveType in the Next Upgrade or I'll freak out.
Someone tell me why they are still all different, please?

Buying all the software (except Motion) from other companies results in what you see in Studio. They did this because it was their interest to do so. Apple bought FCP, originally written for PC's, in what amounted to a fire sale for example.
Would you spend the money (and we're talking a LOT of money) to make them all share a similar UI if you didn't have to? It can be argued that corporate law in this country dictates that Apple cannot spend that dough. How about that notion? LOL...
True, it's tougher to learn Studio because of the different UI's each app has. Development of that might happen as they rewrite all the code. However the cost of doing that in any app at one time is high enough that I can understand why it remains the way it is.
Further, Apple has been and will continue to sell the software anyway, as most users believe it's superior to it's direct competitors in power, stability and in value. Apple won the NLE the unit sales wars a long time ago in any event. Since the market is saturated with FCS users apparently loath to learn (poor souls) a new app, let alone a new suite, there is even less incentive for Apple to spend the dough to do what you'd like to see.
As mentioned above, you can give feedback to Apple. The development teams do read that feedback. I've met some of the folks who cull it inside Apple in fact.
Jerry

Why use an interface?

Hey everybody,
I posted a message in another thread about why to use an abstract class. I have another question and again I am not asking how but why and when. But this time about interfaces. Why would I need to write one? Any example that is not too technical would be great!
I have read a lot about interfaces but mostly it explains how to write one and not when and why to use them.
Thanks in advance for your help!

807479 wrote:
So my question is basically how does implementing an interface help if there is no code in any of the methods?Because it says to anyone who wants to know "this class fulfills the contract for <tt>x</tt>", where <tt>x</tt> is the behaviour (methods) associated with the interface.
Furthermore, in the same way that the language allows you to use a superclass as a type, it also allows you to use interfaces as types.
I presume you're aware that an object can be passed to any method that takes its superclass; well, it can also be passed to any method that takes an interface that it implements.
<tt>String</tt>, for example, implements <tt>Comparable</tt> (a good real-world interface to get familiar with, BTW), so a <tt>String</tt> object can be passed to either of the following methods:public String append(String s)...
public int compareWith(Comparable c)...Now, how does that help you? Suppose you write a program that uses a <tt>List</tt>. A common beginner's mistake is to type everything to the nth degree, viz:ArrayList<String> myList = new ArrayList<String>();and then write methods in the same way:public void addSomeStrings(ArrayList<String> list,
String... items) {.....but, while it will work, it's quite brittle.
Suppose you decide later on that an <tt>ArrayList</tt> isn't the best way to store your Strings ... what do you do? You have to refactor every bit of code that took an <tt>ArrayList</tt> to now take a new type of List (eg, a <tt>LinkedList</tt>).
Suppose instead that you wrote your program as follows:List<String> myList = new ArrayList<String>();and then your methods (hopefully ALL of them) as:public void addSomeStrings(List<String> list,
String... items) {..... Now to change the program to use a <tt>LinkedList</tt>, the ONLY thing you have to change is:List<String> myList = new LinkedList<String>();and your program will work just fine.
This is what a lot of the posts that talk about "programming to interfaces" are on about. It's a very good technique to get familiar with.
HIH
Winston

Why iterator is interface

hi,
why iterator is an interface and not a class.
Thanks,

Iterator is set up as an interface so that you may define iterators of your own for your own classes. Let's assume you create some class MyClass. If this class does not directly extend a class that has a method to return an iterator you would need to define one yourself. So you could create a class MyClassIterator that implements Iterator. Then in MyClass you can add a method as follows:
public class MyClassIterator implements Iterator
MyClass obj = null;
public MyClassIterator(MyClass obj) { this.obj = obj; }
public boolean hasNext() {...}
public Object next() { ... }
public void remove() { ... }
public MyClass
public Iterator iterator()
return new MyClassIterator(this);
}

About Connection, ResultSet, Statement interfaces....

hi ,
Connection, ResultSet, Statement etc.. all are the interfaces. But when i am writing the codes like,
Statement stmt= con.createStatement();
ResultSet rs= stmt.excuteQuery("select * from student_mst");
where con is the instance of Connection interface.
Therefore my question is that since all those(Connection,ResultSet,Statement) are interfaces then how the methods createStatement(),excuteQuery(String sql) are being executed where as those methods are only the declarations in those interfaces,nothing else.

ok.......
So can u tell me in this case, actualy which class is
implenting the Statement interface such that
"executeQuery(String)" is working properly.....??????Hello,
First you need to understand interface and its working.. I will write one example code for u and I think this may hel how Connection, Statement and ResultSet work
This is out main Class
public class Main {
     public static void main(String[] args) {
          Connection con = DriverManager.getConnection();
          Statement stmt = con.createStatement();
          ResultSet rs = stmt.executeQuery("My Query");
          rs.getString();
}Connection.java
public interface Connection {
     public Statement createStatement();
}Statement.java
public interface Statement {
     ResultSet executeQuery(String sql);
}ResultSet.java
public interface ResultSet {
     public String getString();
}DriverManager.java
public class DriverManager {
     public static Connection getConnection()     {
          System.out.println("Calling getConnection()...");
          return new ConnectionImpl();
}Following are the implementstions of the interfaces
ConnectionImpl.java
public class ConnectionImpl implements Connection {
     public Statement createStatement() {
          System.out.println("Calling createStatement()...");
          return new StatementImpl();
}StatementImpl.java
public class StatementImpl implements Statement{
     public ResultSet executeQuery(String sql) {
          System.out.println("Calling executeQuery()...");
          return new ResultSetImpl();
}ResultSetImpl.java
public class ResultSetImpl implements ResultSet{
     public String getString() {
          System.out.println("Calling getString()...");
          return "My String";
}And the Output is
Calling getConnection()...
Calling createStatement()...
Calling executeQuery()...
Calling getString()...
I suppose now you can understand how the Connection, Statement and ResultSet interfaces work

Why we use interfaces ?

hi all!
i m confused that what is the advantage of using interfaces for classes if it is for security,data hiding pupose then we can use private modifiers,then y is this think built in java and which r the cases in which we must use interfaces and y?
plz give me any simple example to understand ur point
thanx in advance.
sajjad ahmad

Hmm... First, I'm sorry about my English... but i will try.
In C++ we can use multi-inheritance that let the developer "extends" one or more classes.
eg.
class Hello extends A,B,C,D
This case can be happened in C++.
But If both class A and B have a method call "void sayMyName()"
How can we refer which method was called when we call "Hello.sayMyName()"
A.sayMyName() or B.sayMyName()
So java don't allow this thing happen.
Java allow developers to extend "only one class"
but to enable multi-inheritance ability Java allow developer to implement more than one class.
That is "interface" which was implemented.
Now lets talk about it's benefits.
Interface is not for security or data hiding purpose.
But interface is used for "make a template".
When I created one class called Hello.
But I have created another class too.
Now I want to make sure that my classed have a method "void say()"
What can I do ?
1. Make some class that have a method "void say()" and let my classes extend it.
2. Make an interface and implement it.
Choise number one is quite good ... but !!!
If I have to extend some another class that is more important such as "Applet"
Now I can't extend another class.
I need only method "void say()". But I don't care what it does.
So I make an interface that force the implementing class to create a method "void say()"
and I implement it.
Question: Why I have to implement this interface ? If I only define a method "void say()"
The problems is gone ....
Answer: That may be true if I want them to have a method. But how can I refer to them.
Lets see this code.
class A extends Applet {
void say() {System.out.println("My name is A");}
... go on ...
class B extends Applet {
void say() {System.out.println("My name is B")}
... go on ...
class GO {
public void letMeSay(............. o) {
o.say();
What can I fill in the argument of method "letMeSay()"?
Object ? Object doesn't have a method "void say()"
Applet ? With the same reason.
Now lets see another code.
interface Sayable {
abstract void say();
class A extends Applet implements Sayable {
void say() {System.out.println("My name is A");}
... go on ...
class B extends Applet implements Sayable {
void say() {System.out.println("My name is B")}
... go on ...
public void letMeSay(Sayable o) {
o.say();
It's ok right ... I can refer to interface "Sayable" that can "say"
Next benefit of interface ... "define Constants field"
We can define constants in an interface and implements it to everywhere we want to use those constants. When we change a value in this interface ... Constants in another place will be changed too .... that is very useful ....(But this may have change in J2SE 1.5 ... see more info)
"I HOPE THIS REPLY MAY GIVE YOU SOME KNOWLEDGE ... GOOD LUCK WITH PROGRAMMING"

Why Re-implements interface?

In Java API, we see such code:
public class ArrayList
extends AbstractList
implements List, RandomAccess, Cloneable, Serializable
My question is, why Sub-class(ArrayList) still declare to re-implement the same inteface(List), since Super-class(AbstractList) already implements it(List)?

sateesh12345 wrote:
If any software programmer write the program to understand anyone. A software engineer makes the problem is simple. By writing the interfaces we can easily understand the what the program, and what the main functionality is in the interface.
I have given a sce::
I we have use the different types printers drives for the windows operating system. In the operating system widows os programmers are written the number of interfaces for the different types of print drivers. when ever we want use the hp printer drivers we can install the hp printer drivers in the os.
In os already hp intrerface is there. That purpose is mainly use the intrerfaces.
what ?!?+_

Why Base and interface tables mandatory column are differant ?

Hi guys , i have load supplier into AP(ap_suppliers) through Interface table(ap_suppliers_int) but my confusion is that ap_suppliers have 8 mandatory columns but it's interface ap_suppliers_int have only 2 mandatory column.why?and also with these 2 columns record is successfully loaded into base so how it's get other mandatory columns value in base table or leave it .
Regards,
Shakeel khan
Edited by: shakeel khan on Mar 14, 2010 8:32 AM

Hi,
Refer to Oracle Payables Reference guide, section "Understanding the Suppliers Open Interface Tables"
Here is an extract:
The intent of the Supplier Open Interface Import is to emulate the entry of Suppliers,
Sites, and Contacts through the Supplier Entry form as closely as possible. As such,
there are many values that will be automatically defaulted if not provided by the user.
These defaults for Suppliers can come from AP_SYSTEM_PARAMETERS_ALL,
FINANCIALS_SYSTEM_PARAMS_ALL, PO_SYSTEM_PARAMETERS.ALL,
RCV_PARAMETERS, or hard-coded values. As these source tables are organized by
operating unit and the supplier data is not, the Suppliers Open Interface Import
program assigns a default organization to each run based on the responsibility of the
user initiating the concurrent request. This is necessary in order to determine which
default values to assign to supplier records.
The defaults for Supplier Sites generally come from the Supplier record. However, in
certain cases due to multiple organizations considerations, it is necessary to default
values for Supplier Sites from AP_SYSTEM_PARAMETERS_ALL or
FINANCIALS_SYSTEM_PARAMS_ALL.
J.

Session Bean - Why the Remote Interface?

Hi,
I have a stateless session bean that takes a serializable object
as a parameter and passes it to an entity bean to persist. My question
is: why should I put the method (addxxx) in the remote interface of my
session bean? Why can't I just put it in the home interface so that I
don't have to instantiate the EJB object first, then call the method?
Any pros/cons? Thanks.
-Linus

You could use the Home.create() method. Generally, the home interface is
used to manage the lifecycle of a EJB. Theoretically, you are right in your
thinking because a stateless session bean does not preserve any state and is
alive for the duration of a method call.
"Linus" <[email protected]> wrote in message
news:[email protected]..
Hi,
I have a stateless session bean that takes a serializable object
as a parameter and passes it to an entity bean to persist. My question
is: why should I put the method (addxxx) in the remote interface of my
session bean? Why can't I just put it in the home interface so that I
don't have to instantiate the EJB object first, then call the method?
Any pros/cons? Thanks.
-Linus

Why ResultSet getDate() method returns null when querying .csv file?

Here is the full code:
import java.sql.*;
import java.sql.Types;
import java.sql.Date;
import myjava.support.CachedRowSetMaker;
import javax.sql.rowset.CachedRowSet;
import java.io.IOException;
import java.text.SimpleDateFormat;
import java.util.Calendar;
class jdbc2{
final private String s1="SELECT top 10 [DATE], [ADJ CLOSE] FROM [vwo-1.csv]";
private ResultSet result=null;
private Connection conn=null;
public static void main(String[] args) throws SQLException{
jdbc2 db=new jdbc2();
try {
          Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
          db.conn = DriverManager.getConnection("jdbc:odbc:STOCK_DATA");
          PreparedStatement sql=db.conn.prepareStatement(db.s1);
          db.result=sql.executeQuery();
// check column names and types using the ResultSetMetaData object.
          ResultSetMetaData metaData = db.result.getMetaData();
     System.out.println("Table Name : " + metaData.getTableName(2));
     System.out.println("Field\t\tDataType");
     for (int i = 0; i < metaData.getColumnCount(); i++) {
     System.out.print(metaData.getColumnName(i + 1) + "\t");
     System.out.println(metaData.getColumnTypeName(i+1));
     System.out.print(metaData.getColumnName(1) + "\t"+metaData.getColumnName(2)+"\n");
          while (db.result.next()){
               System.out.print(db.result.getDate("DATE", Calendar.getInstance()));
               System.out.format("\t%,.2f\n", db.result.getFloat("Adj Close"));
catch (Exception e) {
System.out.println("Error: " + e.getMessage());
     finally {
          db.result.close();
          db.conn.close();
Everything works well, until getting to the block
          while (db.result.next()){
               System.out.print(db.result.getDate("DATE", Calendar.getInstance()));
               System.out.format("\t%,.2f\n", db.result.getFloat("Adj Close"));
The getDate("DATE", Calendar.getInstance())); always returns null, instead of the date value in the vwo-1.csv.
Even though I change it to
java.sql.Date d=db.result.getDate("DATE") and convert to String using .toString(), I still gets nulls. The dollar amount in "Adj Close" field is fine, no problem.
The .csv fils is downloaded from YahooFinace.
Can anyone review the code and shed some light as to what I did wrong?
Thanks alot.

CREATE TABLE `login` (
`username` varchar(40) DEFAULT NULL,
`password` varchar(40) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `amount` (
`amountid` int(11) NOT NULL,
`receiptid` int(11) DEFAULT NULL,
`loanid` int(11) DEFAULT NULL,
`amount` bigint(11) DEFAULT NULL,
`latefee` int(11) DEFAULT NULL,
`paymentid` int(11) DEFAULT NULL,
`pid` int(11) DEFAULT NULL,
PRIMARY KEY (`amountid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `applicationfee` (
`applicationfeeid` int(11) DEFAULT NULL,
`applicationamount` int(11) DEFAULT NULL,
`applicationfee` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `category` (
`categoryid` int(11) DEFAULT NULL,
`categoryname` varchar(40) DEFAULT NULL,
`categorydescription` varchar(500) DEFAULT NULL,
`cattype` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `commission` (
`commissionid` int(11) DEFAULT NULL,
`bussiness` int(11) DEFAULT NULL,
`commission` int(11) DEFAULT NULL,
`pid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `customer` (
`cacno` int(11) NOT NULL DEFAULT '0',
`name` varchar(40) DEFAULT NULL,
`age` int(11) DEFAULT NULL,
`cphone` varchar(40) DEFAULT NULL,
`cmobile` varchar(40) DEFAULT NULL,
`caddress` varchar(500) DEFAULT NULL,
`cstatus` varchar(20) DEFAULT NULL,
`cphoto` longblob,
`pid` int(11) DEFAULT NULL,
PRIMARY KEY (`cacno`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `daybook` (
`closingbal` varchar(40) DEFAULT NULL,
`date` date DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `extraincome` (
`categoryid` int(11) NOT NULL,
`receiptid` int(11) DEFAULT NULL,
`date` date DEFAULT NULL,
`amountid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `employee` (
`empno` int(11) DEFAULT NULL,
`empname` varchar(40) DEFAULT NULL,
`age` int(11) DEFAULT NULL,
`sal` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `image` (
`id` int(11) DEFAULT NULL,
`image` blob
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `loan` (
`loanid` int(11) NOT NULL DEFAULT '0',
`loanamt` varchar(40) DEFAULT NULL,
`payableamount` double DEFAULT NULL,
`installment` int(11) DEFAULT NULL,
`payableinstallments` int(11) DEFAULT NULL,
`monthlyinstallment` varchar(20) DEFAULT NULL,
`surityname` varchar(20) DEFAULT NULL,
`applicationfeeid` int(11) DEFAULT NULL,
`interestrate` float DEFAULT NULL,
`issuedate` date DEFAULT NULL,
`duedate` date DEFAULT NULL,
`nextduedate` date DEFAULT NULL,
`cacno` int(11) DEFAULT NULL,
`cname` varchar(20) DEFAULT NULL,
`pid` int(11) DEFAULT NULL,
`interestamt` double DEFAULT NULL,
`pendingamt` float DEFAULT NULL,
PRIMARY KEY (`loanid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `md` (
`mdid` int(11) NOT NULL DEFAULT '0',
`mdname` varchar(40) DEFAULT NULL,
`mdphoto` varchar(100) DEFAULT NULL,
`mdphone` varchar(40) DEFAULT NULL,
`mdmobile` varchar(40) DEFAULT NULL,
`mdaddress` varchar(500) DEFAULT NULL,
PRIMARY KEY (`mdid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `partner` (
`pid` int(11) NOT NULL DEFAULT '0',
`pname` varchar(40) DEFAULT NULL,
`paddress` varchar(500) DEFAULT NULL,
`pphoto` varchar(100) DEFAULT NULL,
`pphone` varchar(40) DEFAULT NULL,
`pmobile` varchar(40) DEFAULT NULL,
`pstatus` varchar(20) DEFAULT NULL,
`mdid` int(11) DEFAULT NULL,
`mdname` varchar(40) DEFAULT NULL,
`date` date DEFAULT NULL,
`nextpaydate` date DEFAULT NULL,
PRIMARY KEY (`pid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `partnerinvested` (
`pid` int(11) DEFAULT NULL,
`pname` varchar(20) DEFAULT NULL,
`receiptid` int(11) DEFAULT NULL,
`date` date DEFAULT NULL,
`amountinvested` int(11) DEFAULT NULL,
`latefee` int(11) DEFAULT NULL,
`amountid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `payments` (
`paymentid` int(11) NOT NULL,
`categoryid` int(11) DEFAULT NULL,
`particulars` varchar(100) DEFAULT NULL,
`amountid` int(11) DEFAULT NULL,
`paymentdate` date DEFAULT NULL,
PRIMARY KEY (`paymentid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE `receipts` (
`receiptid` int(11) DEFAULT NULL,
`paiddate` date DEFAULT NULL,
`amountid` int(11) DEFAULT NULL,
`loanid` int(11) DEFAULT NULL,
`latefee` int(11) DEFAULT NULL,
`installment` int(11) DEFAULT NULL,
`cacno` int(11) DEFAULT NULL,
`cname` varchar(40) DEFAULT NULL,
`pid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Why resultset is interface

Similar Messages

Maybe you are looking for