persistence

I'm trying to implement a custom session persister in PHP + MySQL. Most of the stuff is trivial - create your DB table, make your read/write functions, call session_set_save_hander() , etc. There are even several tutorials out there that offer sample implementations for you. But somehow all these tutorials have conveniently overlooked one tiny detail about session persisters - locking . And now that's where the real fun starts! I looked at the implementation of session_mysql PECL extension of PHP. That uses MySQL's functions get_lock() and release_lock() . Seems nice, but I don't like the way

Is there any other alternative to SQLite in Android for persisting data in the phone? I am looking something like iOS coredata or something simpler like a key-value store. If we need to embed it with the apps, something that is relatively small in size is also great. Thank you for your assistance. If you need just a simple store for a couple key/value pairs, SharedPreferences is the way to go. If you are looking for something more powerful, that compares to Core Data, you should give greenDAO a try. Like Core Data, greenDAO a layer between your objects and the data store (Core Data on iOS

I'm looking for a solution to transparently persist Perl data structures (not even objects, but object support would be a plus) without circular references. I don't care that much about the backend, but I'd prefer JSON. The number of objects would be relatively low (a few thousands of hashrefs with about 5 keys each). By "transparent" persistence I mean that I don't want to have to commit changes to the storage backend every time I update the in-memory data structure. Here's how the code would ideally look like: my $ds; ... # load the $ds data structure from 'myfile' print $ds->{foo}->{bar}; #

When you develop a Java application that talks to oracle DBs, there are 2 options right? One is oracle thin driver, and the other is OCI driver that requires its own installation (please correct if I'm misunderstanding). Now, what are the pros and cons? Obviously thin driver sounds much better in terms of installation, but is there anything that OCI can and the thin one can't? Develop environment is Tomcat6 + Spring 3.0 + JPA(Hibernate) + apache-DBCP The choice of the driver depends several factors. The nature of your calls to database (e.g. it seem like your app won't be using lots of stored

So I reverse engineered some tables from my db and when I try to save my object to the db I get the following error: Initial SessionFactory creation failed.org.hibernate.AnnotationException: A Foreign key refering com.mycode.Block from com.mycode.Account has the wrong number of column. should be 2 Exception in thread "main" java.lang.ExceptionInInitializerError The Domain objects Are Block which contains a number of Account Objects: @OneToMany(fetch = FetchType.LAZY, mappedBy = "Block") public Set<EAccount> getAccounts() { return this.Accounts; } Account has a Composite key of Id and Role.

Can someone help me write the dependency for javax.persistence . I have googled it but nothing worked. I bumped into this page that gives some details on how to write the dependency, but yet i am unable to write it. Can someone help me out? LeChe This is the one for javax.persistence : <dependency> <groupId>javax.persistence</groupId> <artifactId>persistence-api</artifactId> <version>1.0.2</version> <scope>provided</scope> </dependency> and this is for the whole Java EE 6 stack: <dependency> <groupId>javax</groupId> <artifactId>javaee-api</artifactId> <version>6.0</version> <scope>provided<

I want to add a "Remember Me" check box to the login form of my WPF App. What's the best way to do this? Currently the app logs in via a websevice call that returns an authenticated token that it uses for subsequent calls. Should I simply two-way encrypt and store this token somewhere in the files system? You could also store it in Isolated Storage or create a User setting in your application's Settings. Edit: Oren's suggestion of using DPAPI to protect information is well and good, but it doesn't store anything: An important point to remember is that DPAPI merely applies cryptographic