10 More Discussions You Might Find Interesting
1. AIX
Hi,
What are the differences between concurrent and enhanced concurrent VGs.?
Any advantages of enhanced concurrent VG over normal concurrent vg
Regards,
Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies
2. Solaris
Hi all,
I've been tasked to create a robot account across a bunch of SunOS servers, amongst the requirements for this account is this condition:
Concurrent access requirement
The robot account shall have the ability to create at least ten(10) concurrent access sessions. In order to... (0 Replies)
Discussion started by: dan-e
0 Replies
3. Linux
Hi Guys,
I just wondering if any of the AIX gurus with some exposure to Linux Redhat can tell me whether in Linux ( Red Hat or OpenSuse ) we have a similar option/capability like the CIO (Concurrent I/O) which is currently available on AIX. The reason I'm asking is because in the past we... (2 Replies)
Discussion started by: arizah
2 Replies
4. Shell Programming and Scripting
I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test.
The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies
5. AIX
Hi,
on normal (non concurrent) vgs, it's possible to extend a lun on san-storage , and use chvg -g to rewrite vgda, and use disks with the new size for lvm operations
is the same procedure possbile on a hacmp-cluster (2 node in our case) with concurrent vgs in active/passive mode?
cheers... (5 Replies)
Discussion started by: funksen
5 Replies
6. Shell Programming and Scripting
We have a very large text file..contains almost 100K lines.
We want to process this file to generate another text file as per our data requirement.
As for now the parsing of data takes 20-25 mins each , for 100K lines.
the current script uses :
While Read Each Line
do parsing..
Done
... (6 Replies)
Discussion started by: Amruta Pitkar
6 Replies
7. IP Networking
Just like concurrent tcp server, anyone know how to design the concurrent udp server with the thread? it's best to give some basic examples,thanks (0 Replies)
Discussion started by: Frank2004
0 Replies
8. Shell Programming and Scripting
Hi
I have a ksh that can have multiple instances running at the same time.
The script (each instance) uses the SAME log file to write to.
Should this cause a problem or is the ksh clever enough to queue write requests to the file?
Thanks.
GMMIKE (2 Replies)
Discussion started by: GNMIKE
2 Replies
9. Shell Programming and Scripting
i have a program which uses a java thread that concurrently copies table data with many DB connections (one for each thread)
new to unix, wanted to know if its possible to do a similar thing in a shell script.
for eg
script.sh
trigger 2 stored procs at the same time which are... (6 Replies)
Discussion started by: siva_jm
6 Replies
10. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc workstatin, I am able to login concurrently using a same user ID.
Is there a way to disallow this? That is, at anyone time, the user can have only 1 login session.
How can it be done?
Thanks (10 Replies)
Discussion started by: champion
10 Replies
Alzabo::SQLMaker(3pm) User Contributed Perl Documentation Alzabo::SQLMaker(3pm)
NAME
Alzabo::SQLMaker - Alzabo base class for RDBMS drivers
SYNOPSIS
use Alzabo::SQLMaker::MySQL;
my $sql = Alzabo::SQLMaker::MySQL->new( driver => $driver_object );
# or better yet
my $sql = $runtime_schema->sqlmaker;
DESCRIPTION
This is the base class for all Alzabo::SQLMaker modules. To instantiate a driver call this class's "new" method. See "SUBCLASSING Alz-
abo::SQLMaker" for information on how to make a driver for the RDBMS of your choice.
METHODS
available
Returns A list of names representing the available "Alzabo::SQLMaker" subclasses. Any one of these names would be appropriate as a parame-
ter for the "Alzabo::SQLMaker->load()" method.
load
Load the specified subclass.
This takes one parameter, the name of the RDBMS being used.
Throws: "Alzabo::Exception::Eval"
new
This takes two parameters:
* driver
The driver object being used by the schema.
* quote_identifiers
A boolean value indicating whether or not identifiers should be quoted. This defaults to false.
GENERATING SQL
This class can be used to generate SQL by calling methods that are the same as those used in SQL ("select()", "update()", etc.) in
sequence, with the appropriate parameters.
There are four entry point methods, "select()", "insert()", "update()", and "delete()". Attempting to call any other method without first
calling one of these is an error.
Entry Points
These methods are called as class methods and return a new object.
select ("Alzabo::Table" and/or "Alzabo::Column" objects)
This begins a select. The columns to be selected are the column(s) passed in, and/or the columns of the table(s) passed in as arguments.
Followed by:
"from()"
"** function"
insert
Followed by:
"into()"
update ("Alzabo::Table")
Followed by:
"set()"
delete
Followed by:
"from()"
Other Methods
All of these methods return the object itself, making it possible to chain together method calls such as:
Alzabo::SQLMaker->select($column)->from($table)->where($other_column, '>', 2);
from ("Alzabo::Table" object, ...)
The table(s) from which we are selecting data.
Follows:
"select()"
"** function"
"delete()"
Followed by:
"where()"">
"order_by()"
Throws: "Alzabo::Exception::SQL"
where <see below>
The first parameter to where must be an "Alzabo::Column" object or SQL function. The second is a comparison operator of some sort, given
as a string. The third argument can be an "Alzabo::Column" object, a value (a number or string), or an "Alzabo::SQLMaker" object. The
latter is treated as a subselect.
Values given as parameters will be properly quoted and escaped.
Some comparison operators allow additional parameters.
The "BETWEEN" comparison operator requires a fourth argument. This must be either an "Alzabo::Column" object or a value.
The "IN" and <NOT IN> operators allow any number of additional parameters, which may be "Alzabo::Column" objects, values, or "Alzabo::SQL-
Maker" objects.
Follows:
"from()"
Followed by:
"and()"
"or()"
"order_by()"
Throws: "Alzabo::Exception::SQL"
and (same as "where")
or (same as "where")
These methods take the same parameters as the "where()""> method.
Follows:
"where()"">
"and()"
"or()"
Followed by:
"and()"
"or()"
"order_by()"
Throws: "Alzabo::Exception::SQL"
order_by ("Alzabo::Column" objects)
Adds an "ORDER BY" clause to your SQL.
Follows:
"from()"
"where()"">
"and()"
"or()"
Followed by:
"limit()"
Throws: "Alzabo::Exception::SQL"
limit ($max, optional $offset)
Specifies a limit on the number of rows to be returned. The offset parameter is optional.
Follows:
"from()"
"where()"">
"and()"
"or()"
"order_by()"
"Alzabo::Exception::SQL"
into ("Alzabo::Table" object, optional "Alzabo::Column" objects)
Used to specify what table an insert is into. If column objects are given then it is expected that values will only be given for that
object. Otherwise, it assumed that all columns will be specified in the "values()" method.
Follows:
"insert()"
Followed by:
"values()"
Throws: "Alzabo::Exception::SQL"
values ("Alzabo::Column" object => $value, ...)
This method expects to recive an structured like a hash where the keys are "Alzabo::Column" objects and the values are the value to be
inserted into that column.
Follows:
"into()"
Throws: "Alzabo::Exception::SQL"
set ("Alzabo::Column" object => $value, ...)
This method'a parameter are exactly like those given to the "values" method.
Follows:
"update()"
Followed by:
"where()"">
Throws: "Alzabo::Exception::SQL"
RETRIEVING SQL FROM THE OBJECT
sql
This method can be called at any time, though obviously it will not return valid SQL unless called at a natural end point. In the future,
an exception may be thrown if called when the SQL is not in a valid state.
Returns the SQL generated so far as a string.
bind
Returns an array reference containing the parameters to be bound to the SQL statement.
SUBCLASSING Alzabo::SQLMaker
To create a subclass of "Alzabo::SQLMaker" for your particular RDBMS requires only that the virtual methods listed below be implemented.
In addition, you may choose to override any of the other methods described in this documentation. For example, the MySQL subclass override
the "_subselect()" method because MySQL cannot support sub-selects.
Subclasses are also expected to offer for export various sets of functions matching SQL functions. See the "Alzabo::SQLMaker::MySQL" sub-
class implementation for details.
VIRTUAL METHODS
The following methods must be implemented by the subclass:
limit
See above for the definition of this method.
get_limit
This method may return "undef" even if the "limit()" method was called. Some RDBMS's have special SQL syntax for "LIMIT" clauses. For
those that don't support this, the "Alzabo::Driver" module takes a "limit" parameter.
The return value of this method can be passed in as that parameter.
If the RDBMS does not support "LIMIT" clauses, the return value is an array reference containing two values, the maximum number of rows
allowed and the row offset (the first row that should be used).
If the RDBMS does support "LIMIT" clauses, then the return value is "undef".
sqlmaker_id
Returns the subclass's name. This should be something that can be passed to "Alzabo::SQLMaker->load()" as a parameter.
AUTHOR
Dave Rolsky, <dave@urth.org>
perl v5.8.8 2007-12-23 Alzabo::SQLMaker(3pm)