my dog learned polymorphism
The moose likes JDBC and Relational Databases and the fly likes Dealing with transient information Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Dealing with transient information" Watch "Dealing with transient information" New topic

Dealing with transient information

Jacky Luk
Ranch Hand

Joined: Aug 02, 2012
Posts: 634
One of the user requirements is to mark down the customers
that have never spent since last 6 months.
This is basically done by a joined query.
Now the client asks me how to take care of the customers
whom have been followed but still not yet done any spending afterwards.
They asked me to export a list of customer who haven't spent since last 6 months.
After this list has been followed, the customers, sometimes, will not be dealt with
Do you think it is not good idea to open up another table?
and just dump the list to Excel, and let the user deal with them manually
But if I am, how do I store this kind of information.
The customer table is not a good choice, I think.
What do you think?
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33102

What's wrong with the customer table? You could have an active/inactive flag.

You don't know a customer will go inactive so you don't know the information is transient when it first gets written to the database. And taking it out of the customer table would require you to clean up other tables with foreign keys.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: Dealing with transient information
It's not a secret anymore!