top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

Problem writing record to db using Java

+1 vote
34 views

I am having a problem writing a record to a database. I checked my db connection and that is fine. It just seems this one object will not write to the db

I checked the objects contents and all fields are there. I am using a prepared statement in static class as my data access layer.

posted Sep 2, 2013 by Jai Prakash

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button
Please post the actual error !!

1 Answer

+1 vote

It sounds like you have success writing to other tables? Can you do an insert to that table outside of your app? ...via your db management tool? If so then have you got the data types correct in your mapping?

Seeing the error and the insert statement would help.

answer Sep 4, 2013 by Ahmed Patel
Similar Questions
+2 votes

I have couple of databases named as abc, xyz. If I want to use database "xyz" then type command "use xyz". Command in console show output as "switched to db xyz" but still an user uses commands start with "db" rather than actual name "xyz" why ?

0 votes

I have a Ubuntu server running NGINX that logs data for me. I want to write a python script that reads my customized logs and after a little rearrangement save the new data into my DB (postgresql).

The process should run about every 5 minutes and i'm expecting large chunks of data on several 5 minute windows..

My plan for achieving this is to install python on the server, write a script and add it to cron.

My question is what the simplest way to do this? should I use any python frameworks?
For my python app I'm using Django, but on this server I just need to read a file, do some manipulation and save to DB.

0 votes

Please explain me the basics of mongo db? Also telll me when to Use MongoDB Rather than MySQL (or Other RDBMS)

+2 votes

How can I separate the database DBA user and app access user in rails? The app user will be able to run the app but perform no DDL. The DBA user will be used for migrations.

I do not want the user that runs the rails app to be able to create, drop or modify database objects. This type of user access-rights separation is a pretty minimal best practice and I am concerned that this does not seem to be the norm in the rails world. What am I missing?

My current thinking is that I should create 2 stanzas per database in the database.yml file. One for the dba user and one for the normal app user. Does anyone have any better suggestions?


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.
QUERY HOME
...